Prev: What processor type?
Next: Pushing device/driver binding decisions to userspace
From: Berck E. Nash on 12 Nov 2006 19:20
AHCI pauses heartily on during detection boot, but eventually proceeds.
I've mentioned the problem before, but have since narrowed it down a
bit. The problem does not occur in 2.6.17.3, but does occur in 2.6.18.
The problem is still occurring both in 2.6.19-rc5 as well as
2.6.19-rc5-mm1.

Please cc me on replies since I am not subscribed to LKML.

Messages surrounding the hang:

scsi2 : ahci
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
ata2: port is slow to respond, please be patient (Status 0x80)
ata2: port failed to respond (30 secs, Status 0x80)
ata2: COMRESET failed (device not ready)
ata2: hardreset failed, retrying in 5 secs
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
ata2.00: ata2: dev 0 multi count 1
ata2.00: configured for UDMA/133

I should note that on this system ata1 and ata3 both detect quickly, but
they have 1.5 Gbps devices whereas ata2 has a 3.0Gbps device.

The device:
00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family)
Serial ATA Storage Controller AHCI (rev 01) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. Unknown device 2606
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 50
I/O ports at e400 [size=8]
I/O ports at e080 [size=4]
I/O ports at e000 [size=8]
I/O ports at dc00 [size=4]
I/O ports at d880 [size=16]
Memory at febfb800 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>

dmesg snip from 2.6.17.3, without the hangup:

scsi1 : ahci
ata2: port reset, p_is 40000001 is 2 pis 0 cmd 4017 tf 451 ss 123 se 0
ata2: SATA link up 3.0 Gbps (SStatus 123)
ata2: dev 0 cfg 49:2f00 82:0068 83:5060 84:4000 85:0000 86:1000 87:4000
88:407f
ata2: dev 0 ATA-6, max UDMA/133, 640 sectors: LBA
ata2: dev 0 configured for UDMA/133


Thanks,
Berck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Tejun Heo on 15 Nov 2006 07:50
Berck E. Nash wrote:
> AHCI pauses heartily on during detection boot, but eventually proceeds.
> I've mentioned the problem before, but have since narrowed it down a
> bit. The problem does not occur in 2.6.17.3, but does occur in 2.6.18.
> The problem is still occurring both in 2.6.19-rc5 as well as
> 2.6.19-rc5-mm1.
>
> Please cc me on replies since I am not subscribed to LKML.
>
> Messages surrounding the hang:
>
> scsi2 : ahci
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: qc timeout (cmd 0xec)
> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
> ata2: port is slow to respond, please be patient (Status 0x80)
> ata2: port failed to respond (30 secs, Status 0x80)
> ata2: COMRESET failed (device not ready)
> ata2: hardreset failed, retrying in 5 secs
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: ATA-6, max UDMA/133, 640 sectors: LBA
> ata2.00: ata2: dev 0 multi count 1
> ata2.00: configured for UDMA/133
>
> I should note that on this system ata1 and ata3 both detect quickly, but
> they have 1.5 Gbps devices whereas ata2 has a 3.0Gbps device.

Hmmm.. Can you try with the attached patch applied? Also, please turn
on kernel config 'Kernel Hacking -> Show timing info on printks' and
report boot dmesg.

Thanks.

--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Berck E. Nash on 15 Nov 2006 13:30
Tejun Heo wrote:
> Hmmm.. Can you try with the attached patch applied? Also, please turn
> on kernel config 'Kernel Hacking -> Show timing info on printks' and
> report boot dmesg.

Looks like you forgot to attach the patch, so I couldn't test it:)
Here's the section with the annoying hang with timing info. I noticed
that there are similar messages repeated later, but without as much
hang, so I've attached the entire dmesg as well, in case it's of any help.

[ 74.774249] scsi2 : ahci
[ 75.232531] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 105.197121] ata2.00: qc timeout (cmd 0xec)
[ 105.197168] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x104)
[ 113.040691] ata2: port is slow to respond, please be patient (Status
0x80)
[ 135.973052] ata2: port failed to respond (30 secs, Status 0x80)
[ 135.973098] ata2: COMRESET failed (device not ready)
[ 135.973145] ata2: hardreset failed, retrying in 5 secs
[ 141.836829] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 142.366267] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100)
[ 143.171270] ata2: SATA link down (SStatus 0 SControl 300)

Berck
From: Tejun Heo on 26 Nov 2006 22:40
On Wed, Nov 15, 2006 at 11:22:23AM -0700, Berck E. Nash wrote:
> Tejun Heo wrote:
> >Hmmm.. Can you try with the attached patch applied? Also, please turn
> >on kernel config 'Kernel Hacking -> Show timing info on printks' and
> >report boot dmesg.
>
> Looks like you forgot to attach the patch, so I couldn't test it:)
> Here's the section with the annoying hang with timing info. I noticed
> that there are similar messages repeated later, but without as much
> hang, so I've attached the entire dmesg as well, in case it's of any help.

Yeah, I did and forgot about this thread too. Sorry. This is on the
top of my to-do list now. I'm attaching the patch. TIA.

--
tejun
From: Berck E. Nash on 27 Nov 2006 04:00
Tejun Heo wrote:

> Yeah, I did and forgot about this thread too. Sorry. This is on the
> top of my to-do list now. I'm attaching the patch. TIA.

That didn't fix the problem, but did change the messages. I've attached
the entire log, including the weird errors on power-off from the same
device that gives problems on boot, which I suspect are related.

Berck
 |  Next  |  Last
Pages: 1 2 3
Prev: What processor type?
Next: Pushing device/driver binding decisions to userspace