[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080128134404.24c80ce7.akpm@linux-foundation.org>
Date: Mon, 28 Jan 2008 13:44:04 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: netdev@...r.kernel.org
Cc: bugme-daemon@...zilla.kernel.org,
Auke Kok <auke-jan.h.kok@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
t.artem@...lcity.com
Subject: Re: [Bugme-new] [Bug 9836] New: e1000 network driver doesn't
recognize (and load on) its hardware
On Mon, 28 Jan 2008 05:32:00 -0800 (PST)
bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9836
>
> Summary: e1000 network driver doesn't recognize (and load on) its
> hardware
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.24
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@...ox.com
> ReportedBy: t.artem@...lcity.com
>
>
> Latest working kernel version: not known
> Earliest failing kernel version: every
> Distribution: Fedora Core 7
> Hardware Environment: lspci output and dmesg information are attached
> Software Environment: doesn't matter
> Problem Description: recently e1000 network drivers stopped working when right
> after switching on or rebooting our Intel server. While trying to 'modprobe
> e1000; ifconfig eth0 IP_address' I've got a failure and e1000 says hardware is
> not detected. After about a *hundred* attempts to modprobe and rmmod it, the
> e1000 network driver finally loads and allows to set up networking.
>
> Steps to reproduce: reboot or power on your server. Try to up the network which
> is attached to your Intel PCI-X Pro 1000 NIC.
>
Odd.
--
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
Powered by blists - more mailing lists