From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [RFT] major libata update
Date: Wed, 17 May 2006 15:35:04 +0900 [thread overview]
Message-ID: <446AC418.4070704@gmail.com> (raw)
In-Reply-To: <446AB12C.10001@gmail.com>
Tejun Heo wrote:
> Andrew Morton wrote:
>> No. In fact, it doesn't even work with the 2.6.17-rc4-mm1 lineup plus
>> the
>> latest git-libata-all. It needs this tweak:
>>
>> --- devel/drivers/scsi/ata_piix.c~2.6.17-rc4-mm1-ich8-fix
>> 2006-05-16 18:36:12.000000000 -0700
>> +++ devel-akpm/drivers/scsi/ata_piix.c 2006-05-16
>> 18:36:12.000000000 -0700
>> @@ -542,6 +542,14 @@ static unsigned int piix_sata_probe (str
>> port = map[base + i];
>> if (port < 0)
>> continue;
>> + if (ap->flags & PIIX_FLAG_AHCI) {
>> + /* FIXME: Port status of AHCI controllers
>> + * should be accessed in AHCI memory space. */
>> + if (pcs & 1 << port)
>> + present_mask |= 1 << i;
>> + else
>> + pcs &= ~(1 << port);
>> + }
>> if (ap->flags & PIIX_FLAG_IGNORE_PCS || pcs & 1 << (4 + port))
>> present_mask |= 1 << i;
>> else
The above patch doesn't do anything. The only effect it has is setting
present_mask according to enabled bits instead of present bits. I think
this patch might have helped with probing before the MAP tables for
ICH6/7 are fixed.
I've done further testing.
* Symptom
ata_piix tries to probe non-existing slave device resulting in timeouts
during boot probing. This problem is aggravated by new probing updates
as it retries two more times before giving up.
* Test results
PATA never has any problem with device detection via signature. Only
SATA is affected and interestingly only ATAPI device. The following is
the test result on my machine (ICH7R + PX716SA).
1. combined mode : MAP [IDE IDE P1 P3]
P1 P3
-----------------------------
PX716-SA empty P3 ghosted as ATAPI device
empty PX716-SA okay
PX716-SA HDD okay
HDD PX716-SA okay
2. SATA-only mode : MAP [P0 P2 P1 P3]
P0 P2
-----------------------------
PX716-SA empty P2 ghosted as ATAPI device
empty PX716-SA okay
PX716-SA HDD okay
HDD PX716-SA okay
P1 P3
-----------------------------
Identical to #1.
To sum up, it happens when the master slot is occupied by an ATAPI
device and the corresponding slave slot is empty. The slave slot
reports ATAPI signature (probably duplicated from the master) and passes
all legacy presence test thus resulting in timeout on IDENTIFY.
In all above cases, the PCS register reported correct presence masks.
* Proposed solution
It seems that the only solution is to make use of the PCS presence bits
somehow. It is know that 6300ESB family of controllers have flaky
presence bits (ata_piix marks them with PIIX_FLAG_IGNORE_PCS), but I
couldn't find any document/errata for PCS bits for any other
controllers. So, we can use PCS for all !PIIX_FLAG_IGNORE_PCS
controllers or take a conservative approach and make use of it only on
cases where ghosting problem is reported (ICH7 and 8, I guess. Can
anyone test 6?).
Please note that we already use some use of the PCS value when probing
SATA port. If its value is zero, we skip the port. It's done this way
mainly due to historical reasons - until recently ata_piix didn't have
MAP tables to map PM/PS/SM/SS to specific ports thus used the PCS values
in rougher form.
Jeff, what do you think?
--
tejun
next prev parent reply other threads:[~2006-05-17 6:35 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 17:00 [RFT] major libata update Jeff Garzik
2006-05-15 17:18 ` Andrew Morton
2006-05-15 18:06 ` Jeff Garzik
2006-05-15 19:06 ` Arkadiusz Miskiewicz
2006-05-15 20:45 ` Jeff Garzik
2006-05-15 19:33 ` Mark Lord
2006-05-15 22:52 ` Tejun Heo
2006-05-15 18:15 ` Jeff Garzik
2006-05-15 18:27 ` Andrew Morton
2006-05-15 18:44 ` Jeff Garzik
2006-05-15 18:37 ` Alan Cox
2006-05-15 17:19 ` Alan Cox
2006-05-15 17:13 ` Jeff Garzik
2006-05-15 18:29 ` Tomasz Torcz
2006-05-15 18:43 ` Jeff Garzik
2006-05-15 23:32 ` Tejun Heo
2006-05-15 23:49 ` Jeff Garzik
2006-05-16 0:04 ` Tejun Heo
2006-05-16 2:15 ` Tejun Heo
2006-05-15 19:15 ` Jeff Garzik
2006-05-15 23:02 ` Wakko Warner
2006-05-15 23:00 ` Jeff Garzik
2006-05-15 23:13 ` Wakko Warner
2006-05-15 23:19 ` Jeff Garzik
2006-05-15 23:40 ` Alan Cox
2006-05-15 23:50 ` Wakko Warner
2006-05-15 23:38 ` Alan Cox
2006-05-15 23:47 ` Wakko Warner
2006-05-15 23:45 ` Jeff Garzik
2006-05-15 23:30 ` Avuton Olrich
2006-05-15 23:36 ` Tejun Heo
2006-05-15 23:54 ` Jeff Garzik
2006-05-16 0:08 ` Avuton Olrich
2006-05-16 3:36 ` Avuton Olrich
2006-05-16 3:51 ` Jeff Garzik
2006-05-16 4:33 ` Avuton Olrich
2006-05-16 14:57 ` Linus Torvalds
2006-05-17 15:25 ` OGAWA Hirofumi
2006-05-17 23:40 ` Linus Torvalds
2006-05-17 23:48 ` Jeff Garzik
2006-05-18 1:48 ` Alan Cox
2006-05-17 23:49 ` Linus Torvalds
2006-05-16 15:02 ` Jeff Garzik
2006-05-16 3:55 ` Tejun Heo
2006-05-16 4:37 ` Avuton Olrich
2006-05-16 11:36 ` Ric Wheeler
2006-05-16 14:25 ` Jeff Garzik
2006-05-16 15:24 ` Tejun Heo
2006-05-16 18:29 ` Ric Wheeler
2006-05-16 21:41 ` Ric Wheeler
2006-05-16 22:02 ` Jeff Garzik
2006-05-16 23:11 ` Eric D. Mudama
2006-05-17 2:13 ` Ric Wheeler
2006-05-16 23:23 ` Tejun Heo
2006-05-17 2:09 ` Ric Wheeler
2006-05-16 23:44 ` Tejun Heo
2006-05-16 23:53 ` Jeff Garzik
2006-05-17 0:00 ` Jeff Garzik
2006-05-17 0:29 ` Tejun Heo
2006-05-17 1:08 ` Jeff Garzik
2006-05-17 1:27 ` Tejun Heo
2006-05-17 2:26 ` Jeff Garzik
2006-05-17 3:05 ` Tejun Heo
2006-05-22 7:19 ` Jeff Garzik
2006-05-23 13:59 ` Tejun Heo
2006-05-17 0:31 ` Jeff Garzik
2006-05-17 0:50 ` Tejun Heo
2006-05-17 0:57 ` Tejun Heo
2006-05-17 2:22 ` Ric Wheeler
2006-05-17 1:37 ` Tejun Heo
2006-05-17 3:57 ` Ric Wheeler
2006-05-17 4:44 ` Tejun Heo
2006-05-17 11:30 ` Ric Wheeler
2006-05-17 20:45 ` Ric Wheeler
2006-05-17 21:01 ` Mark Lord
2006-05-17 21:04 ` Jeff Garzik
2006-05-17 21:50 ` Tejun Heo
2006-05-17 21:56 ` Mark Lord
2006-05-17 22:00 ` Jeff Garzik
2006-05-17 22:03 ` Mark Lord
2006-05-17 22:13 ` Jeff Garzik
2006-05-18 3:33 ` Ric Wheeler
2006-05-18 3:26 ` Tejun Heo
2006-05-18 11:58 ` Ric Wheeler
2006-05-18 12:52 ` Mark Lord
2006-05-18 13:22 ` Ric Wheeler
2006-05-18 13:37 ` Jens Axboe
2006-05-17 1:13 ` Jeff Garzik
2006-05-17 1:14 ` Jeff Garzik
2006-05-17 2:16 ` Ric Wheeler
2006-05-16 23:34 ` Jeff Garzik
2006-05-16 23:53 ` Tejun Heo
2006-05-17 2:05 ` Andrew Morton
2006-05-17 4:49 ` Tejun Heo
2006-05-17 4:56 ` Andrew Morton
2006-05-17 5:14 ` Tejun Heo
2006-05-17 6:35 ` Tejun Heo [this message]
2006-05-18 11:24 ` Albert Lee
2006-05-18 11:33 ` Tejun Heo
2006-05-19 10:37 ` Albert Lee
2006-05-19 11:03 ` Tejun Heo
2006-05-22 3:51 ` [PATCH 1/1] libata: use polling pio for identify device Albert Lee
2006-05-22 6:24 ` Jeff Garzik
2006-05-23 2:27 ` Albert Lee
2006-05-18 23:07 ` [RFT] major libata update Andrew Morton
2006-05-19 1:14 ` Tejun Heo
2006-05-19 2:06 ` Jeff Garzik
2006-05-19 2:16 ` Tejun Heo
2006-05-22 7:22 ` Jeff Garzik
2006-05-21 23:51 ` Michael Sterrett -Mr. Bones.-
2006-05-22 2:42 ` Tejun Heo
2006-05-22 3:42 ` Michael Sterrett -Mr. Bones.-
2006-05-22 6:23 ` Michael Sterrett -Mr. Bones.-
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 7:35 Matthieu CASTET
2006-05-18 0:36 Brown, Len
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=446AC418.4070704@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).