PF + BRIDGE + PFSYNC causes system freezing

[Max Laier]

On Thursday 18 March 2010 15:04:06 Giulio Ferro wrote:
> On 17.03.2010 18:00, Max Laier wrote:
> > Can you enable WITNESS and compile in DDB. Make sure to report any LORs
> >
> >>> and once the system freezes try to enter the debugger and get ps and
> >>> locks information.
> >>>
> >>> show allchains
> >>> show alllocks
> >>> ps
> >>>
> >>> After that you can try to "call doadump" so you get the information in
> >>> the coredump and don't have to transcribe it manually.
> >>>
> >>> Thanks,
> >>>     Max
> >>
> >> Sorry, I'm not really an expert of this, but how can I enter the
> >> debugger if the system has frozen?
> >
> > Ctrl+Alt+ESC (in default configuration).
> > _______________________________________________
> 
> I've added this  to the kernel
> 
> option          KDB
> option          WITNESS
> option          WITNESS_KDB

remove WITNESS_KDB, it's not what you want.

> option          DDB
> 
> 
> Now it can't even boot properly. It stops when it tries to configure
> networking:
> uma_zalloc_arg: zone "256" with the following non-sleepable locks held:
> exclusive rw ifnet_rw (ifnet_rw) r = 0 (0xffffffff80e31b20) locked @
> /usr/src/sys/net/if.c:414

a "bt" would help in this case to see where the bad alloc is.

> show allchains
> <no result>
> 
> show alllocks
> exclusive rw ifnet_rw (ifnet_rw) r = 0 (0xffffffff80e31b20) locked @
> /usr/src/sys/net/if.c:414
> exclusive sx ifnet_sx (ifnet_sx) r = 0 (0xffffffff80e31b40) locked @
> /usr/src/sys/net/if.c:414
> 
> ps
> <returns a lot of stuff. tell me to search something in particular>
> 
> call doadump
> Cannot dump. Device not defined or unavailable

define "dumpdev" in rc.conf to a swap partition with enough space or call 
dumpon(8).

Thanks,
  Max