Re: tcpdump bpf_catchpacket crash

2015-10-01 Thread Hrvoje Popovski
On 1.10.2015. 11:24, Martin Pieuchot wrote: > On 01/10/15(Thu) 11:11, Hrvoje Popovski wrote: >> On 1.10.2015. 0:43, Stuart Henderson wrote: >>> In /sys/ddb/db_trap.c line 72, change if(panicstr != NULL) to if(1), it >>> should give you a backtrace and short ps (showing only the active process >>>

Re: tcpdump bpf_catchpacket crash

2015-10-01 Thread Martin Pieuchot
On 01/10/15(Thu) 11:11, Hrvoje Popovski wrote: > On 1.10.2015. 0:43, Stuart Henderson wrote: > > In /sys/ddb/db_trap.c line 72, change if(panicstr != NULL) to if(1), it > > should give you a backtrace and short ps (showing only the active process > > on each cpu). These are now done automatically

Re: tcpdump bpf_catchpacket crash

2015-10-01 Thread Hrvoje Popovski
On 1.10.2015. 0:43, Stuart Henderson wrote: > In /sys/ddb/db_trap.c line 72, change if(panicstr != NULL) to if(1), it > should give you a backtrace and short ps (showing only the active process on > each cpu). These are now done automatically for panics, but not for other ddb > entries (which in

Re: tcpdump bpf_catchpacket crash

2015-09-30 Thread Stuart Henderson
In /sys/ddb/db_trap.c line 72, change if(panicstr != NULL) to if(1), it should give you a backtrace and short ps (showing only the active process on each cpu). These are now done automatically for panics, but not for other ddb entries (which includes uvm faults). On 30 September 2015 23:30:02 B

tcpdump bpf_catchpacket crash

2015-09-30 Thread Hrvoje Popovski
Hi, I have tested mp ix patches and at one point very naively, i did tcpdump on interface on which i generate traffic :) and everything is fine until i quit tcpdump with ^C, then crash happened. traffic is generated at high rate (10Mpps). this crash is 100% reproducible. in ddb console i can't do a