Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763368AbYCFL5e (ORCPT ); Thu, 6 Mar 2008 06:57:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757938AbYCFL5Y (ORCPT ); Thu, 6 Mar 2008 06:57:24 -0500 Received: from mail.gmx.net ([213.165.64.20]:35497 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757758AbYCFL5X (ORCPT ); Thu, 6 Mar 2008 06:57:23 -0500 X-Authenticated: #20450766 X-Provags-ID: V01U2FsdGVkX1/AroUxNAfADgO5/GJ8+GTb+PNzOsos7ITx+mhFl+ GBD27W6zwGnj8A Date: Thu, 6 Mar 2008 12:57:32 +0100 (CET) From: Guennadi Liakhovetski To: Tejun Heo cc: Alan Cox , linux-kernel@vger.kernel.org, Jeff Garzik , linux-ide@vger.kernel.org Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6 In-Reply-To: <47CFADDF.20200@gmail.com> Message-ID: References: <20080228225603.2764bfd1@core> <47CFADDF.20200@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4169 Lines: 83 On Thu, 6 Mar 2008, Tejun Heo wrote: > Guennadi Liakhovetski wrote: > > Indeed! It was in "IDE" mode, and 2 out of the 3 chips were handled by the > > piix driver (btw, why did Intel put 3 different SATA controllers on one > > board?). I switched it to AHCI mode (the third possibility is RAID) and > > indeed a kernel with (only) ahci driver managed to bring them up! > > Although, the eSATA link was "slow to respond": > > > > ata4: port is slow to respond, please be patient (Status 0x80) > > ata4: softreset failed (device not ready) > > ata4: port is slow to respond, please be patient (Status 0x80) > > ata4: softreset failed (device not ready) > > ata4: port is slow to respond, please be patient (Status 0x80) > > ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100 > > ata4.00: 312581808 sectors, multi 16: LBA48 > > ata4.00: applying bridge limits > > ata4.00: configured for UDMA/100 > > > > but then it did manage it. Is such a delay normal? > > If you hotplugged it, sometimes drives don't respond too well and takes > a few retries to talk to it. I've seen this messages both on cold- and hot-plug. > How long did the whole thing take? Here's a hot-plug log: Mar 4 15:04:28 6a kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xa frozen Mar 4 15:04:28 6a kernel: ata4: irq_stat 0x00000040, connection status changed Mar 4 15:04:28 6a kernel: ata4: SError: { PHYRdyChg CommWake DevExch }Mar 4 15:04:28 6a kernel: ata4: hard resetting link Mar 4 15:04:38 6a kernel: ata4: softreset failed (device not ready) Mar 4 15:04:38 6a kernel: ata4: hard resetting link Mar 4 15:04:48 6a kernel: ata4: softreset failed (device not ready) Mar 4 15:04:48 6a kernel: ata4: hard resetting link Mar 4 15:04:55 6a kernel: ata4: port is slow to respond, please be patient (Status 0x80) Mar 4 15:05:20 6a kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 15:05:20 6a kernel: ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100 Mar 4 15:05:20 6a kernel: ata4.00: 312581808 sectors, multi 0: LBA48 Mar 4 15:05:20 6a kernel: ata4.00: applying bridge limits Mar 4 15:05:20 6a kernel: ata4.00: configured for UDMA/100 Mar 4 15:05:20 6a kernel: ata4: EH complete Mar 4 15:05:20 6a kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD1600BB-00R 20.0 PQ: 0 ANSI: 5 Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write Protect is off Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 4 15:05:20 6a kernel: sdb: sdb1 sdb2 Mar 4 15:05:20 6a kernel: sd 3:0:0:0: [sdb] Attached SCSI disk Mar 4 15:05:20 6a kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0 Looks like almost a minute to me? On another occurence I see about 1.5 minutes, then "port is slow to respond, please be patient (Status 0x80)" has been repeated 3 times. On cold-plug also 3 times, I think, about the same time then (time is not updated in the log). > And is it always like that? So far - yes. > > One more question, what do UDMA numbers mean in SATA context? The internal > > SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2. > > 1.00 is port 1 device 00 and UDMA numbers don't mean much to SATA devices. Sorry, I actually meant to ask what "UDMA/133" means for a SATA link? Thanks Guennadi --- Guennadi Liakhovetski -- 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/