On Fri, 2013-06-07 at 20:34 +0200, Steinar H. Gunderson wrote: > On Fri, Jun 07, 2013 at 02:26:08PM -0400, Steven Rostedt wrote: > > On Fri, 2013-06-07 at 19:52 +0200, Steinar H. Gunderson wrote: > > Ah, that's because of this: module_init(ipgre_init); Where it makes it > > into: > > > > 00000000 <init_module>: > > 0: 55 push %ebp > > 1: 89 e5 mov %esp,%ebp > > 3: 53 push %ebx > > 4: 83 ec 08 sub $0x8,%esp > > 7: c7 04 24 00 00 00 00 movl $0x0,(%esp) > > a: R_386_32 .rodata.str1.4 > > > > We can use ipgre_tap_init_net, and the offset of 0xb032 (45106) as that > > was 0xffffffffa0e5d034 - 0xffffffffa0e52002. Do you have CONFIG_NET_NS > > set? > > ipgre_tap_init_net is 000000000000001a, but there's no way I can subtract > 0xb053 from that? Sorry, I'm confused. :-)
OK, then its most likely in another module (likely the ip_tunnel.ko). Do know if you have CONFIG_NET_NS set in your .config? > > > You can also cat /proc/modules. It gives you where the modules are > > located. > > I've booted back to 3.9.x already; I couldn't live with a crashing kernel like > that. Unfortunately it's not that easy for me to reboot this machine all the > time either. :-/ OK, if you get time, this may be a candidate to do a git bisect with. Thanks, -- Steve -- 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/
