From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: networking probs in next-20081203
Date: Wed, 3 Dec 2008 17:18:34 -0800 [thread overview]
Message-ID: <20081203171834.86903d39.akpm@linux-foundation.org> (raw)
x86_64, CONFIG_E1000E=y.
Current Linus mainline is OK, but with linux-next I'm seeing the following:
- During boot I see a "cannot open /proc/net/dev" fly past. But when
it gets to the login prompt, I can read /proc/net/dev.
- Networking won't come up. `ifup eth0' says "determining ip address
... failed", and the failure is immediate.
- eth0 appears in the ifconfig oputput as normal - it just won't come up.
- nothing interesting in dmesg
Here's the dmesg: http://userweb.kernel.org/~akpm/dmesg-dead-net.txt
(that dmesg was generated with E1000=y, E1000E=y, but that doesn't seem
to matter)
The .config: http://userweb.kernel.org/~akpm/config-dead-net.txt
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next reply other threads:[~2008-12-04 1:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 1:18 Andrew Morton [this message]
2008-12-04 15:14 ` networking probs in next-20081203 Alexey Dobriyan
2008-12-04 17:41 ` Kok, Auke
2008-12-04 17:52 ` Alexey Dobriyan
2008-12-04 18:11 ` [E1000-devel] " Stephen Smalley
2008-12-04 18:21 ` David Miller
2008-12-04 19:32 ` Stephen Smalley
2008-12-04 20:06 ` Stephen Smalley
2008-12-04 21:00 ` [E1000-devel] " Eric W. Biederman
2008-12-05 2:03 ` James Morris
2008-12-05 7:49 ` Eric W. Biederman
2008-12-05 14:12 ` Stephen Smalley
2008-12-11 10:41 ` James Morris
2008-12-12 5:24 ` Alexey Dobriyan
2008-12-12 9:26 ` James Morris
2008-12-12 9:29 ` James Morris
2008-12-12 10:51 ` Eric W. Biederman
2008-12-12 21:40 ` [E1000-devel] " James Morris
2008-12-12 21:24 ` Stephen Smalley
2008-12-15 13:28 ` James Morris
2008-12-19 1:04 ` [PATCH 0/3][RFC] Fix security and SELinux handling of proc/* filesystems James Morris
2008-12-19 1:05 ` [PATCH 1/3][RFC] SELinux: correctly detect proc filesystems of the form "proc/foo" James Morris
2008-12-19 12:29 ` David P. Quigley
2008-12-19 1:06 ` [PATCH 2/3][RFC] security: pass mount flags to security_sb_kern_mount() James Morris
2008-12-19 12:52 ` Stephen Smalley
2008-12-19 1:07 ` [PATCH 3/3][RFC] SELinux: don't check permissions for kernel mounts James Morris
2008-12-19 12:52 ` Stephen Smalley
2008-12-19 6:40 ` [PATCH 0/3][RFC] Fix security and SELinux handling of proc/* filesystems David Miller
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=20081203171834.86903d39.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).