At Tue, 23 Dec 2008 22:49:24 +0200,
Vladimir V. Kobal wrote:
>
> We are using pf+ALTQ for shaping and ipfw for filtering, diverting into
> netgraph nodes, attaching altq queues.
>
OK, that also makes sense given what I saw in the code. Can you
explain your entire setup? That is, which filters,
, 2008 9:36 PM
To: Vladimir V. Kobal
Cc: freebsd-net@freebsd.org
Subject: Re: Panic on boot with em1 attached
OK, that narrows it down. Are you using any filtering such as PF,
ipfw, etc.?
Best,
George
___
freebsd-net@freebsd.org mailing list
http
At Tue, 23 Dec 2008 13:57:39 +0200,
Vladimir V. Kobal wrote:
>
> With fastforwarding off the system works well and boots without panicing.
>
OK, that narrows it down. Are you using any filtering such as PF,
ipfw, etc.?
Best,
George
___
freebsd-net@fre
: Monday, December 22, 2008 5:28 PM
To: Vladimir V. Kobal
Cc: freebsd-net@freebsd.org
Subject: Re: Panic on boot with em1 attached
Hi,
Can you try this with fastforwarding off? It looks like a double free
somewhere in the ip_fastforward() routine. Someone frees m but does
not NULL it out and at
Hi,
Can you try this with fastforwarding off? It looks like a double free
somewhere in the ip_fastforward() routine. Someone frees m but does
not NULL it out and at the drop: label the mbuf m is valid but the
data within it has already been freed. Knowing if this is related
only to the fast for
Hello,
System is a NAS and has two interfaces. Default route is on em0. The network
consisting of 2k hosts is attached to the em1. 7.0-RELEASE, 7.1-BETA2,
7.1-RC1
has the same error. In the progress of boot (uptime 7 seconds) it is
panicing:
Slab at 0xff000152ef50, freei 2 = 0.
panic: Duplica
