Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756028AbYFAIg5 (ORCPT ); Sun, 1 Jun 2008 04:36:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751650AbYFAIgp (ORCPT ); Sun, 1 Jun 2008 04:36:45 -0400 Received: from aun.it.uu.se ([130.238.12.36]:50102 "EHLO aun.it.uu.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751602AbYFAIgm (ORCPT ); Sun, 1 Jun 2008 04:36:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18498.24460.411071.234025@harpo.it.uu.se> Date: Sun, 1 Jun 2008 10:36:28 +0200 From: Mikael Pettersson To: Stephen Hemminger Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: sky2 unsupported chip type 0xff failure X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 16129 Lines: 311 I mentioned earlier that the sky2 chip in my ASUS P5B-E Plus sometimes doesn't get recognized on a cold boot. Well, today it happened again (first time in over a week). This is with the 2.6.26-rc4 kernel: >sky2 0000:02:00.0: enabling device (0000 -> 0003) >ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17 >PCI: Setting latency timer of device 0000:02:00.0 to 64 >sky2 0000:02:00.0: unsupported chip type 0xff >ACPI: PCI interrupt for device 0000:02:00.0 disabled >sky2: probe of 0000:02:00.0 failed with error -95 Here's an lspci dump of the device when it isn't recognized: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 12) Subsystem: ASUSTeK Computer Inc. Unknown device 81f8 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-