From: Stephen Hemminger <shemminger@vyatta.com>
To: "Graham, David" <david.graham@intel.com>
Cc: "Hillier,
Gernot "
<IMCEAMAILTO-gernot+2Ehillier+40siemens+2Ecom@intel.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Hockert, Jeff W" <jeff.w.hockert@intel.com>,
"Graham, David" <david.graham@intel.com>
Subject: Re: e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3
Date: Wed, 8 Oct 2008 23:36:30 +0200 [thread overview]
Message-ID: <20081008233630.53d26853@speedy> (raw)
In-Reply-To: <E3627BC91D010645BD262A1E8720005106A64162@orsmsx420.amr.corp.intel.com>
On Wed, 8 Oct 2008 08:25:49 -0700
"Graham, David" <david.graham@intel.com> wrote:
> Hi Gernot,
>
> Thanks for reporting this issue. We have witnessed this in our labs too,
> only on platforms that have BMC management firmware. I'm very familiar
> with the problem, and believe that we have fixed it, though the
> application of the fix may not be simple. The problem is a result of
> improper synchronization between the platform FW and the e1000e driver
> when they attempt concurrent access to LAN resources, and fixes were
> made both on the driver side, and on the FW side. On some platforms a
> simple driver update resolves the problem, others require FW fixes too.
>
> The 0.2.0 driver in 2.6.25 has no fixes for this problem, and so I am
> not surprised that you see it there. The first set of changes for this
> issue are already in the 0.3.3.3-k2 driver that you are still seeing the
> problem with on 2.6.26, so either those changes are not good, or your
> issue requires one of the additional fixes.
>
> There have been further improvements made to the driver synchronization
> code since the 0.3.3.3-k2 driver, and it is possible that a newer driver
> would resolve the issue. It'd be good for us to know if that's the case.
> The driver version is not yet (AFAICS) upstream, but is already
> available in the standalone e1000e-0.4.1.7 driver on sourceforge.
> (google "sourceforge e1000e"). Would you be able to try that, as a first
> step ?
Repeat rant heard from many users and vendors:
Why does Intel continue to not do driver development in mainline kernel?
next prev parent reply other threads:[~2008-10-08 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EA929A9653AAE14F841771FB1DE5A1365F498F4EDC@rrsmsx501.amr.corp.intel.com>
2008-10-08 15:25 ` e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3 Graham, David
2008-10-08 21:36 ` Stephen Hemminger [this message]
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
2008-10-07 14:25 Hillier, Gernot
2008-10-08 10:29 ` Krzysztof Halasa
2008-10-08 13:35 ` Hillier, Gernot
2008-10-08 22:03 ` Krzysztof Halasa
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=20081008233630.53d26853@speedy \
--to=shemminger@vyatta.com \
--cc=IMCEAMAILTO-gernot+2Ehillier+40siemens+2Ecom@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=david.graham@intel.com \
--cc=jeff.w.hockert@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 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.