Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754400AbYJGOUh (ORCPT ); Tue, 7 Oct 2008 10:20:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753370AbYJGOUa (ORCPT ); Tue, 7 Oct 2008 10:20:30 -0400 Received: from goliath.siemens.de ([192.35.17.28]:18160 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753040AbYJGOU3 (ORCPT ); Tue, 7 Oct 2008 10:20:29 -0400 Message-ID: <48EB7161.60004@siemens.com> Date: Tue, 07 Oct 2008 16:25:37 +0200 From: "Hillier, Gernot" Organization: Siemens AG, CT SE 2 User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.9) Gecko/20070801 SUSE/2.0.0.9-0.1 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 MIME-Version: 1.0 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 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1964 Lines: 47 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 -- 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/