On Thu, Jun 06, 2013 at 11:06:48PM -0400, Steven Rostedt wrote: > Note the faulting address is 0xffffffffa0e52001, which is around the > above address, be interesting to know what was at that location.
Aha, the plot thickens: root 6095 0.0 0.0 6632 596 ? D Jun06 0:00 /sbin/modprobe -q -- net-pf-17 pannekake:/usr/src/linux-3.10-rc4> sudo cat /proc/6095/stack [<ffffffff812bb04f>] register_pernet_subsys+0x18/0x39 [<ffffffffa0ffd089>] packet_init+0x32/0x44 [af_packet] [<ffffffff81000263>] do_one_initcall+0x7b/0x10c [<ffffffff8107e5db>] load_module+0x1b1f/0x1e19 [<ffffffff8107e969>] SyS_init_module+0x94/0xa1 [<ffffffff8138cf12>] system_call_fastpath+0x16/0x1b [<ffffffffffffffff>] 0xffffffffffffffff I have a tcpdump running almost all the time (from boot), for a variety of reasons. And I think I have the BPF JIT on; possibly related. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
