From: Andrew Morton <akpm@linux-foundation.org>
To: jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com,
bruce.w.allan@intel.com, peter.p.waskiewicz.jr@intel.com,
john.ronciak@intel.com, e1000-devel@lists.sourceforge.net
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
tuharsky@misbb.sk, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 13568] New: Intel e1000 4-port NIC - unable to communicate, slowly blinking
Date: Mon, 29 Jun 2009 16:00:03 -0700 [thread overview]
Message-ID: <20090629160003.ea299eb5.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13568-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 18 Jun 2009 13:45:38 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13568
>
> Summary: Intel e1000 4-port NIC - unable to communicate, slowly
> blinking
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.30
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Network
> AssignedTo: drivers_network@kernel-bugs.osdl.org
> ReportedBy: tuharsky@misbb.sk
> Regression: No
>
>
> Hallo,
>
> I have here Tyan GT20 (B2865G20S4H) barebone server with onboard GbE NICs
> (Broadcom BCM5721 and Marvell 88E1111-CAA PHY).
>
> I have installed PCI-E Intel__ PRO/1000 PT Quad Port Server Adapter
> (EXPI9404PTBLK) to gain 6 ports altogether. This is the card:
>
> http://www.intel.com/products/server/adapters/pro1000pt-quadport/pro1000pt-quadport-overview.htm
>
> Now, with Debian 5.0 Lenny (distributional kernel 2.6.26), only the onboard
> cards are functional. The Intel is also recognised by the kernel, is assigned
> ports (eth2-5), however none of them works when connected to network. The NIC
> is aware of plugging or un-plugging the cable (displays message on console),
> however no communication is ever performed, and the connected port just lazily
> blinks.
>
> After some rochades hard to reproduce (plugging, unplugging, configuring
> interfaces, resetting etc), it even worked for few seconds, and then died out
> again forever.
>
> I have also compiled fresh 2.6.30 kernel, no advance however. Interesting, that
> ifconfig always revails huge number of errors for the port.
>
------------------------------------------------------------------------------
next parent reply other threads:[~2009-06-29 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13568-10286@http.bugzilla.kernel.org/>
2009-06-29 23:00 ` Andrew Morton [this message]
2009-06-29 23:32 ` [Bugme-new] [Bug 13568] New: Intel e1000 4-port NIC - unable to communicate, slowly blinking 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=20090629160003.ea299eb5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bruce.w.allan@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=tuharsky@misbb.sk \
/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).