From: Tejun Heo <htejun@gmail.com>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
Jeff Garzik <jeff@garzik.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Date: Thu, 27 Sep 2007 10:05:23 +0900 [thread overview]
Message-ID: <46FB01D3.2020002@gmail.com> (raw)
In-Reply-To: <46FA6B29.3030807@gmail.com>
Berck E. Nash wrote:
> Bernd Schmidt wrote:
>> One of these appears in my system as well (ASUS P5W-DH Deluxe
>> mainboard). Here's the hdparm output:
>
> Yup, same mainboard here.
>
>> Since about 2.6.17 or 2.6.18, it has been causing long delays while
>> booting:
>> 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=0x5)
>> ata2: port is slow to respond, please be patient (Status 0x80)
>> ata2: COMRESET failed (errno=-16)
>> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata2.00: ATA-6: Config Disk, RGL10364, max UDMA/133
>> ata2.00: 640 sectors, multi 1: LBA
>> ata2.00: configured for UDMA/133
>
> And yup, same problem with the painful boot delays since 2.6.18. Tejun
> indicated that a fix would get merged with 2.6.23, but that didn't
> happen. Here's hoping something makes it into .24!
Yeah, it is the sil4726 virtual device which is really crappy as an ATA
device. About the fix, I thought PMP support would fix it but the
controller on P5W-DH doesn't support PMP. It can only talk to the
virtual device or the device attached to the first port depending on how
the PMP chip is configured. It seems we'll have to blacklist the
mainboard and skip or use modified reset sequence on the affected port,
so that's why the fix was delayed. I'm currently on the road but I'll
look into it when I get back (next week).
Thanks.
--
tejun
next prev parent reply other threads:[~2007-09-27 4:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 18:02 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot Berck E. Nash
2007-09-25 1:37 ` Jeff Garzik
2007-09-25 18:14 ` Berck E. Nash
2007-09-25 18:21 ` Jens Axboe
2007-09-25 18:28 ` Berck E. Nash
2007-09-25 18:32 ` Jens Axboe
2007-09-25 19:29 ` Berck E. Nash
2007-09-25 20:40 ` Jeff Garzik
2007-09-25 22:07 ` Berck E. Nash
2007-09-25 22:46 ` Berck E. Nash
2007-09-26 1:21 ` Jeff Garzik
2007-09-26 2:25 ` Berck E. Nash
2007-09-26 2:33 ` Jeff Garzik
2007-09-26 4:40 ` Jeff Garzik
2007-09-26 10:03 ` Bernd Schmidt
2007-09-26 14:22 ` Berck E. Nash
2007-09-27 1:05 ` Tejun Heo [this message]
2007-09-26 14:19 ` Berck E. Nash
2007-10-03 21:18 ` Jeff Garzik
[not found] <fa.7B5oGGPZtkIAG9trDHdybt+z9Qg@ifi.uio.no>
[not found] ` <fa.lh2GEsFivC+TeMBqgRXU+5p7ySM@ifi.uio.no>
[not found] ` <fa.tqIC/0YXN2BDEJQ7WBFuJ0EEUrI@ifi.uio.no>
[not found] ` <fa.Q/HeymU0u7VpG+dN5Lc1DraTos0@ifi.uio.no>
2007-09-25 22:39 ` Robert Hancock
2007-09-26 1:10 ` Jeff Garzik
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=46FB01D3.2020002@gmail.com \
--to=htejun@gmail.com \
--cc=bernds_cb1@t-online.de \
--cc=flyboy@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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 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).