On Wed, 14 May 2003 12:59:23 -0700 (PDT) "David S. Miller" <davem@redhat.com> wrote: | From: Jens Axboe <axboe@suse.de> | Date: Wed, 14 May 2003 15:08:38 +0200 | | This half-assed back-out from bk current makes it work here, Arnaldo | could you please fix this?? | | This is a good clue, thanks for tracking it down this far. | I'll help figure out what's wrong, I can reproduce the problem | here too. | | I believe the problem has something to do with changing when the | rtnetlink/netlink init runs, not the socket owner stuff. Ah, init ordering. If it involvles initcalls (I see ./netlink/af_netlink.c:subsys_initcall(netlink_proto_init);), you can set initcall_debug=1 on the kernel command line to get a list of initcall addresses dumped into the syslog. Then you can grep those lines and convert them to names using http://www.xenotime.net/linux/scripts/cvrt_initcalls which calls http://www.xenotime.net/linux/scripts/ksysmap if that will help you any. -- ~Randy - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
