From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ICH8 and SATA
Date: Tue, 23 May 2006 08:39:57 +0900 [thread overview]
Message-ID: <44724BCD.10509@gmail.com> (raw)
In-Reply-To: <44724952.4040003@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> Jeff Garzik wrote:
>>> BTW, Intel sez:
>>>
>>> "FYI, I added PIIX_FLAG_IGNORE_PCS and was able to boot on ICH8."
>>>
>>
>> Yeap, that should achieve about the same effect as the experimental
>> patch Andrew posted; also, about the same phantom bug.
>
> Nod, just sending that to note conclusively that ICH8+PCS is a confirmed
> problem case, as confirmed from multiple sources.
>
>
>> I don't think the phantom device problem is caused by missing
>> dev_select. We have enough dev_select() during classification.
>
> Just a guess. Can I easily reproduce this? I have a bunch of Intel
> machines, ICH5/6/7 (no ICH8 yet), of various flavors.
>
I can reliably reproduce it using ICH7 (ASUS P5LD2). The problem occurs
on both combined and sata-only modes. On my machine, combined mode maps
secondary master and slave to P1 and P3, respectively. And, of course,
SATA only mode maps to PM, PS, SM, SS to P0, P2, P1, P3.
In either mode, occupy the master slot (P0 or P1) with an ATAPI device
(I use PX716-SA) and leave the slave slot (P2 or P3) empty. The
signature of the ATAPI device is duplicated on the empty slave slot. As
noted before, this doesn't occur if the master device is ATA, only the
slave slot is occupied or both are occupied.
--
tejun
next prev parent reply other threads:[~2006-05-22 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 7:35 ICH8 and SATA Jeff Garzik
2006-05-22 22:04 ` Tejun Heo
2006-05-22 23:29 ` Jeff Garzik
2006-05-22 23:39 ` Tejun Heo [this message]
2006-05-23 2:12 ` Albert Lee
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=44724BCD.10509@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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).