From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
Auke Kok <auke-jan.h.kok@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
t.artem@mailcity.com
Subject: Re: [Bugme-new] [Bug 9836] New: e1000 network driver doesn't recognize (and load on) its hardware
Date: Mon, 28 Jan 2008 13:44:04 -0800 [thread overview]
Message-ID: <20080128134404.24c80ce7.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9836-10286@http.bugzilla.kernel.org/>
On Mon, 28 Jan 2008 05:32:00 -0800 (PST)
bugme-daemon@bugzilla.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@pobox.com
> ReportedBy: t.artem@mailcity.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.
next parent reply other threads:[~2008-01-28 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9836-10286@http.bugzilla.kernel.org/>
2008-01-28 21:44 ` Andrew Morton [this message]
2008-01-28 22:23 ` [Bugme-new] [Bug 9836] New: e1000 network driver doesn't recognize (and load on) its hardware Brandeburg, Jesse
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=20080128134404.24c80ce7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=t.artem@mailcity.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.