Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756961AbYJHVht (ORCPT ); Wed, 8 Oct 2008 17:37:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756677AbYJHVgl (ORCPT ); Wed, 8 Oct 2008 17:36:41 -0400 Received: from mail.vyatta.com ([76.74.103.46]:54419 "EHLO mail.vyatta.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756888AbYJHVgj (ORCPT ); Wed, 8 Oct 2008 17:36:39 -0400 Date: Wed, 8 Oct 2008 23:36:30 +0200 From: Stephen Hemminger To: "Graham, David" Cc: "Hillier, Gernot " , , , "Allan, Bruce W" , "Hockert, Jeff W" , "Graham, David" Subject: Re: e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3 Message-ID: <20081008233630.53d26853@speedy> In-Reply-To: References: Organization: Vyatta X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.9; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1831 Lines: 36 On Wed, 8 Oct 2008 08:25:49 -0700 "Graham, David" 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/