From: David Miller <davem@davemloft.net>
To: akpm@osdl.org
Cc: miles.lane@gmail.com, dcbw@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jeremy@goop.org, rml@novell.com
Subject: Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an "eth" device name
Date: Mon, 28 Aug 2006 13:27:17 -0700 (PDT) [thread overview]
Message-ID: <20060828.132717.57158097.davem@davemloft.net> (raw)
In-Reply-To: <20060828120328.ae734de0.akpm@osdl.org>
From: Andrew Morton <akpm@osdl.org>
Date: Mon, 28 Aug 2006 12:03:28 -0700
> grepping for `ioctl' gives:
>
> ioctl(9, SIOCGIWNAME, 0xbfe38d8c) = -1 EINVAL (Invalid argument)
> ioctl(9, SIOCETHTOOL, 0xbfe38d2c) = 0
> ioctl(11, SIOCGIFHWADDR, {ifr_name="eth0", ???}) = -1 ENODEV (No such device)
> ioctl(11, SIOCGIFFLAGS, {ifr_name="eth0", ???}) = -1 ENODEV (No such device)
>
> Perhaps you could generate the strace output for 2.6.18-rc5, grep that for
> ioctl, look for differences? That initial SIOCGIWNAME failure is fishy.
That might help, but SIOCGIWNAME just gets a string that
says what wireless mode the device is in, not the device
name. Althought NetworkManager might use this for something
interesting.
All of the interesting config calls are probably happening
via netlink, which doesn't get decoded by strace.
But changes via netlink can get traced by using "ip" in monitor mode,
try "ip monitor all" as root during such a NetworkManager run.
next prev parent reply other threads:[~2006-08-28 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0608270007gc6a919fx9e36562d8023635d@mail.gmail.com>
2006-08-27 7:19 ` Andrew Morton
2006-08-27 7:38 ` David Miller
2006-08-28 15:52 ` Miles Lane
2006-08-28 19:03 ` Andrew Morton
2006-08-28 20:27 ` David Miller [this message]
[not found] ` <a44ae5cd0608290143m3ad300eej5b325270c9d57b66@mail.gmail.com>
2006-08-29 9:26 ` David Miller
2006-08-27 16:30 ` Jeremy Fitzhardinge
2006-08-28 14:32 ` Benoit Boissinot
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=20060828.132717.57158097.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dcbw@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rml@novell.com \
/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
all inboxes | Powered by JetHome®