linux-kernel - Re: 2.6.18 - AHCI detection pauses excessively

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Nov 2006 21:45:11 +0900
From:	Tejun Heo <htejun@...il.com>
To:	"Berck E. Nash" <flyboy@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18 - AHCI detection pauses excessively

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/