From: "Hillier, Gernot" <gernot.hillier@siemens.com>
To: jesse.brandeburg@intel.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bruce.w.allan@intel.com
Subject: e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3
Date: Tue, 07 Oct 2008 16:25:37 +0200 [thread overview]
Message-ID: <48EB7161.60004@siemens.com> (raw)
Hi there,
On at least two machines using the Supermicro X7DB3 board with Intel
82563EB (a.k.a. PCI device 8086:1096), we see sporadic problems on modprobe
(about 1 time in some hundred tries):
e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
e1000e 0000:06:00.0: setting latency timer to 64
0000:06:00.0: 0000:06:00.0: Hardware Error
0000:06:00.0: eth0: (PCI Express:2.5GB/s:Width x4) 00:30:48:67:f5:f6
0000:06:00.0: eth0: Intel(R) PRO/1000 Network Connection
0000:06:00.0: eth0: MAC: 3, PHY: 5, PBA No: 2050ff-0ff
e1000e 0000:06:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
e1000e 0000:06:00.1: setting latency timer to 64
0000:06:00.1: eth1: (PCI Express:2.5GB/s:Width x4) 00:30:48:67:f5:f7
0000:06:00.1: eth1: Intel(R) PRO/1000 Network Connection
0000:06:00.1: eth1: MAC: 3, PHY: 5, PBA No: 2050ff-0ff
0000:06:00.0: eth0: Hardware Error
eth0 is not available after module loading. During boot, this means the
machine won't come up correctly. Problem can be "fixed" by removing and
reloading the module.
This happens on the rather old SUSE-patched 2.6.25.11 with e1000e 0.2.0 as
well as with vanilla 2.6.27-rc8 including e1000e 0.3.3.3-k2.
The machines are equipped with two Quad-Core Xeons E5440 and 8GB of RAM.
Both kernels are compiled for x86_64.
Supermicro claims that there's no known hardware problem with these boards
and that the Windows driver doesn't show any issue...
Is there anything I can do to help narrowing down the problem? Anything I
can test? Any help greatly appreciated...
TIA!
--
Gernot Hillier
Siemens AG, CT SE 2, Corporate Competence Center Embedded Linux
next reply other threads:[~2008-10-07 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 14:25 Hillier, Gernot [this message]
2008-10-08 10:29 ` e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3 Krzysztof Halasa
2008-10-08 13:35 ` Hillier, Gernot
2008-10-08 22:03 ` Krzysztof Halasa
[not found] <EA929A9653AAE14F841771FB1DE5A1365F498F4EDC@rrsmsx501.amr.corp.intel.com>
2008-10-08 15:25 ` Graham, David
2008-10-08 21:36 ` Stephen Hemminger
2008-10-09 13:18 ` Hillier, Gernot
2008-10-14 9:18 ` Gernot Hillier
2008-10-15 16:37 ` Graham, David
2008-10-16 12:32 ` Hillier, Gernot
2008-10-16 16:07 ` Hillier, Gernot
2008-11-11 10:05 ` Hillier, Gernot
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=48EB7161.60004@siemens.com \
--to=gernot.hillier@siemens.com \
--cc=bruce.w.allan@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).