> On 10 Mar 2021, at 10:07, Mamontov Roman wrote:
>
> Hello.
>
> I try to use netdump(4) option for transmitting kernel dumps to a remote
> server.
> When I caused a kernel panic by sysctl debug.kdb.panic I found, that
> netdumping
> to remote server happens very slow: systat -ifstat o
08.02.2021, 20:10, "Marek Zarychta" :
> W dniu 08.02.2021 o 19:32, Alexander V. Chernikov pisze:
>> 08.02.2021, 14:33, "Marek Zarychta" :
>>> W dniu 08.02.2021 o 13:10, mike tancsa pisze:
>>>> I have been setting up some tests to s
08.02.2021, 14:33, "Marek Zarychta" :
> W dniu 08.02.2021 o 13:10, mike tancsa pisze:
>> I have been setting up some tests to see if
>>
>> option FIB_ALGO and dpdk_lpm4.ko
>>
>> will help with my pkt forwarding needs and large routing tables. So far so
>> good. But one thing I noticed, is that
08.02.2021, 12:10, "mike tancsa" :
> I have been setting up some tests to see if
>
> option FIB_ALGO and dpdk_lpm4.ko
>
> will help with my pkt forwarding needs and large routing tables. So far so
> good. But one thing I noticed, is that its very chatty to dmesg.
> eg
> alloc_nhgrp: new mpath grou
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
18.07.2020, 14:22, "Alexander V. Chernikov" :
> Dear FreeBSD users,
>
> I would like to make net.add_addr_allfibs=0 as the default system behaviour
> and remove net.add_addr_allfibs.
> To do so, I would like to collect use cases with net.add_addr_allfibs=1 and
> multi
15.04.2020, 15:10, "Kristof Provost" :
> On 15 Apr 2020, at 15:34, Kristof Provost wrote:
>> On 15 Apr 2020, at 0:37, Li-Wen Hsu wrote:
>>> (Please send the followup to freebsd-testing@ and note Reply-To is
>>> set.)
>>>
>>> FreeBSD CI Weekly Report 2020-04-12
>>> ===
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
19.05.2015, 03:22, "Marcelo Gondim" :
> Hi all,
Hi,
>
> I see that there is still the following bug in ipfw:
>
> # ipfw table 33 add 0.0.0.0/8
> # ipfw table 33 list
> ::/8 0
>
> and
>
> # ipfw table 33 add 255.255.255.255
> # ipfw table 33 list
> ::/8 0
>
> The IP 255.255.255.255 not appear but it
On 25.03.2013 02:38, Alexander V. Chernikov wrote:
> On 24.03.2013 07:11, Eric van Gyzen wrote:
>> At work, we discovered that our application's IPMI thread would often
>> use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so
>> it can run without sleep
On 24.03.2013 07:11, Eric van Gyzen wrote:
At work, we discovered that our application's IPMI thread would often
use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so
it can run without sleeping for a "long" time with a slow BMC. It also
holds the ipmi_softc.ipmi_lock during th
On 10.10.2012 00:36, Guy Helmer wrote:
On Oct 8, 2012, at 8:09 AM, Guy Helmer wrote:
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
I'm not seeing how bd_sbuf would be NULL here. Any ideas?
Since I've not had any replies, I hope nobody minds if I reply with more
information.
Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.10.2011 13:50, Steven Hartland wrote:
> - Original Message - From: "Li, Qing"
>
>>> RTM_MISS: Lookup failed on this address: len 184, pid: 0, seq 0, errno
>>> 0, flags:
>>> locks: inits:
>>> sockaddrs:
>>> ::A.B.C.D
>>>
I'm unable to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Cox wrote:
> On 08/20/2011 12:41, Kostik Belousov wrote:
>> On Sat, Aug 20, 2011 at 12:33:29PM -0500, Alan Cox wrote:
>>> On Thu, Aug 18, 2011 at 3:16 AM, Alexander V.
>>> Chernikovwrote:
>>>
On 10.08.2011 19:16, per...@pluto.rain.com wrote:
On 10.08.2011 19:16, per...@pluto.rain.com wrote:
Chuck Swiger wrote:
On Aug 9, 2011, at 7:26 AM, Daniel Kalchev wrote:
I am trying to set up 64GB partitions for swap for a system that
has 64GB of RAM (with the idea to dump kernel core etc). But, on
8-stable as of today I get:
WARNING: reduc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kurt Jaeger wrote:
> Hi!
>
>>> Can someone have a look at
>>>
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=154469
>>>
>>> and commit it ? So that it ends up in 8.3 8-} ?
>> Does the patch from OpenBSD fix the problem for you?
>
> Yes, sure. That wh
Doug Barton wrote:
On 01/24/10 03:02, Harald Schmalzbauer wrote:
Alexander V. Chernikov schrieb am 24.01.2010 10:24 (localtime):
Please try to rebuild port with
post-configure:
@${REINPLACE_CMD} -e 's/^\(CFLAGS .*\)-O2 \(.*\)$$/\1 -O0 \2/'
${WRKSRC}/nss/Makefile
That should be pr
Harald Schmalzbauer wrote:
Alexander V. Chernikov schrieb am 24.01.2010 10:24 (localtime):
...
gdb /usr/bin/top top.core
bt
And sure a backtrace from the top built with -g would be much better.
cd /usr/src/usr.bin/top
CFLAGS=-g make
Unfortunately nss_ldap seems to be the culprit.
There is
Harald Schmalzbauer wrote:
Mikolaj Golub schrieb am 22.01.2010 23:26 (localtime):
On Wed, 20 Jan 2010 08:06:23 +0100 Harald Schmalzbauer wrote:
Dear all,
I have no idea why top crashes with segmentation fault on my amd64
machine running FreeBSD 8.0-RELEASE-p2.
If someone wants to have a loot
Daniel Corrigan wrote:
Since this was released to a public mailing list, I can only assume some
less than nice user will attempt this.
The only top level file system I have that can be written to by normal users
is /tmp
Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from causing
harm
20 matches
Mail list logo
