On 03/12/13 08:49, David Holland wrote: [---] > > Dec 3 03:15:46 aria syslogd[188]: restart > > Dec 3 03:15:46 aria /netbsd: uvm_fault(0xffffffff8071b4d8, 0x0, 1) -> e > > Dec 3 03:15:46 aria /netbsd: fatal page fault in supervisor mode > > Dec 3 03:15:46 aria /netbsd: trap type 6 code 0 rip ffffffff8031162f cs > > 8 rflags 10283 cr2 60 cpl 4 rsp fffffe8004cf9b98 > > Dec 3 03:15:46 aria /netbsd: panic: trap > > Dec 3 03:15:46 aria /netbsd: cpu1: Begin traceback... [---] > > Trap 6 = illegal op-code? Should I start worrying about broken RAM > > modules? > > from sys/arch/x86/include/trap.h: > #define T_PAGEFLT 6 /* page fault */ > > and %cr2 contains 60, so in all probability it's just a null pointer > dereference.
Oh; thanks. > If you use objdump -d or nm -n or gdb or whatever to find the code > that's at 0xffffffff8031162f in your kernel, you'll probably get a > fairly good idea of what broke. A lot of pf_state_* around there, so it looks like packet filter is croaking. Ugh.. pf seems slightly broken for other reasons as well (rules are ignored sometimes), and I know others have mentioned it in the past. Do I file a PR? /Jan
