On Wed, Dec 03, 2008 at 05:18:34PM -0800, Andrew Morton wrote:
> 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.
I _suspect_ it might me something with /proc/net changes (again) and initcall
ordering.
Andrew, as rejectless quick test, you can do
git checkout -f 26b0d981e7dd1d5b4852ed5719bd1388c7994163 # sic
which is the last tree merged before proc tree in that next tree.
> - 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=/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
