LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
Date: Thu, 6 Mar 2008 12:57:32 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803061248070.5670@axis700.grange> (raw)
In-Reply-To: <47CFADDF.20200@gmail.com>

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

  reply	other threads:[~2008-03-06 11:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 22:37 Guennadi Liakhovetski
2008-02-28 22:56 ` Alan Cox
2008-02-28 23:33   ` Guennadi Liakhovetski
2008-03-06  8:39     ` Tejun Heo
2008-03-06 11:57       ` Guennadi Liakhovetski [this message]
2008-03-06 18:02         ` Gaston, Jason D
2008-03-06 18:05           ` Jeff Garzik
2008-03-06 18:40             ` Guennadi Liakhovetski
2008-03-07  4:51         ` Tejun Heo
2008-03-08 22:47           ` Guennadi Liakhovetski
2008-03-09  5:14             ` Tejun Heo
2008-03-09 21:24               ` Guennadi Liakhovetski
2008-03-10  0:50                 ` Tejun Heo
2008-03-10  7:22                   ` Guennadi Liakhovetski
2008-03-10 13:05                     ` Tejun Heo
2008-03-11 10:11                       ` Guennadi Liakhovetski
2008-03-11 10:35                         ` Tejun Heo
2008-03-11 11:13                           ` Guennadi Liakhovetski
2008-03-11 11:37                             ` Tejun Heo
2008-02-29  0:23   ` Felix Miata
2008-02-29  3:50     ` Gaston, Jason D

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0803061248070.5670@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Unknown SATA PIIX PCI device ID 0x29b6' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).