Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750743AbVLNRLh (ORCPT ); Wed, 14 Dec 2005 12:11:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751120AbVLNRLh (ORCPT ); Wed, 14 Dec 2005 12:11:37 -0500 Received: from xenotime.net ([66.160.160.81]:41867 "HELO xenotime.net") by vger.kernel.org with SMTP id S1750743AbVLNRLg (ORCPT ); Wed, 14 Dec 2005 12:11:36 -0500 Date: Wed, 14 Dec 2005 09:11:30 -0800 (PST) From: "Randy.Dunlap" X-X-Sender: rddunlap@shark.he.net To: Bernhard Rosenkraenzer cc: linux-kernel@vger.kernel.org Subject: Re: sata_uli fails to see harddisks on an ASRock 939Dual-SATA2 board In-Reply-To: <200512141501.10093.bero@arklinux.org> Message-ID: References: <200512141501.10093.bero@arklinux.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1492 Lines: 38 On Wed, 14 Dec 2005, Bernhard Rosenkraenzer wrote: > On an ASRock 939Dual-SATA2 board, the sata_uli driver recognizes the onboard > SATA controller (PCI ID 10b9:5289 rev 10, Subsystem 1849:5289), but fails to > see an attached harddisk (the BIOS identifies the harddisk correctly, so a > hardware failure is unlikely). sata_uli apparently sees _something_ is > attached, but doesn't get further. dmesg says: > > libata version 1.20 loaded. > sata_uli 0000:00:12.1: version 0.5 > GSI 18 sharing vector 0xD1 and IRQ 18 > ACPI: PCI Interrupt 0000:00:12.1[A] -> GSI 19 (level, low) -> IRQ 209 > ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE082 bmdma 0xD880 irq 209 > ata2: SATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdma 0xD888 irq 209 > ata1: SATA link up 1.5 Gbps (SStatus 113) > scsi0 : sata_uli > ata2: SATA link down (SStatus 0) > scsi1 : sata_uli > > No disks are found, even though the link (on ata1) is detected. > > Verified both with an x86 and an x86_64 kernel, and both 2.6.15-rc5 and > 2.6.15-rc5-mm2. > > Any ideas? I've seen this and thought that it was MSI interrupt related. I have suggested disabling CONFIG_PCI_MSI, but (iirc) that did not fix the problem for someone who tested it. I'll fiddle with it some... no promises. -- ~Randy - 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/