netdev - networking probs in next-20081203

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Dec 2008 17:18:34 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	netdev@...r.kernel.org, e1000-devel@...ts.sourceforge.net
Subject: networking probs in next-20081203


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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html