From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org, acme@conectiva.com.br
Subject: Re: 2.5 qdisc problem
Date: Wed, 14 May 2003 13:05:08 -0700 [thread overview]
Message-ID: <20030514130508.4c6ece84.rddunlap@osdl.org> (raw)
In-Reply-To: <20030514.125923.102559449.davem@redhat.com>
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
next prev parent reply other threads:[~2003-05-14 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 7:06 Jens Axboe
2003-05-14 12:26 ` Zephaniah E. Hull
2003-05-14 12:59 ` Jens Axboe
2003-05-14 13:08 ` Jens Axboe
2003-05-14 19:59 ` David S. Miller
2003-05-14 20:05 ` Randy.Dunlap [this message]
2003-05-14 20:14 ` David S. Miller
2003-05-15 7:54 ` Jens Axboe
2003-05-14 19:29 ` Jose Luis Domingo Lopez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030514130508.4c6ece84.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=acme@conectiva.com.br \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome