From: Tejun Heo <htejun@gmail.com>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18 - AHCI detection pauses excessively
Date: Wed, 15 Nov 2006 21:45:11 +0900 [thread overview]
Message-ID: <455B0BD7.20108@gmail.com> (raw)
In-Reply-To: <4557B7D2.2050004@gmail.com>
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
next prev parent reply other threads:[~2006-11-15 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 0:09 2.6.18 - AHCI detection pauses excessively Berck E. Nash
2006-11-15 12:45 ` Tejun Heo [this message]
2006-11-15 18:22 ` Berck E. Nash
2006-11-23 11:20 ` JG
2006-11-27 3:35 ` Tejun Heo
2006-11-27 8:58 ` Berck E. Nash
2006-11-29 8:55 ` Tejun Heo
2006-11-29 18:53 ` Berck E. Nash
2006-11-29 19:27 ` Mark Lord
2006-12-01 7:07 ` Tejun Heo
2006-12-01 13:35 ` Berck E. Nash
2006-12-01 13:59 ` Tejun Heo
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=455B0BD7.20108@gmail.com \
--to=htejun@gmail.com \
--cc=flyboy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.