From: David Milburn <dmilburn@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: mikpe@it.uu.se, tj@kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH #sx4] sata_sx4: fixup interrupt handling
Date: Thu, 14 May 2009 09:07:20 -0500 [thread overview]
Message-ID: <4A0C2598.9090503@redhat.com> (raw)
In-Reply-To: <4A0B5768.7000309@garzik.org>
Jeff Garzik wrote:
> David Milburn wrote:
>
>> Issuing ATA_CMD_SET_FEATURES (0xef) times out because
>> pdc20621_interrupt ignores command completion since
>> ATA_TFLAG_POLLING flag is set.
>>
>> This has already been fixed for sata_promise:
>>
>> commit 51b94d2a5a90d4800e74d7348bcde098a28f4fb3
>> Author: Tejun Heo <htejun@gmail.com>
>> Date: Fri Jun 8 13:46:55 2007 -0700
>>
>> sata_promise: use TF interface for polling NODATA commands
>>
>> Also, this patch includes Mikael's original patches:
>>
>> http://marc.info/?l=linux-ide&m=121135828227724&w=2
>> http://marc.info/?l=linux-ide&m=121144512109826&w=2
>>
>> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
>> Signed-off-by: David Milburn <dmilburn@redhat.com>
>> ---
>> drivers/ata/sata_sx4.c | 22 +++++++++-------------
>> 1 files changed, 9 insertions(+), 13 deletions(-)
>
>
> Oh, and: does vanilla upstream sata_sx4 work at all?
Jeff,
It does not work on 2.6.30-rc5
Linux version 2.6.30-rc5
.
.
.
ata1.00: ATA-6: ST3160023AS, 3.05, max UDMA/133
ata1.00: 312581808 sectors, multi 0: LBA48
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
ata1.00: ATA-6: ST3160023AS, 3.05, max UDMA/133
ata1.00: 312581808 sectors, multi 0: LBA48
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
ata1.00: limiting speed to UDMA/133:PIO3
ata1.00: ATA-6: ST3160023AS, 3.05, max UDMA/133
ata1.00: 312581808 sectors, multi 0: LBA48
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
ata1.00: disabled
Same thing if I drop in sata_sx4.c and libata-sff.c
changes from libata-dev sx4 branch.
But, after applying this patch on top of that
ata1.00: ATA-6: ST3160023AS, 3.05, max UDMA/133
ata1.00: 312581808 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3160023AS 3.05 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
ata2.00: NODEV after polling detection
ata3.00: NODEV after polling detection
ata4.00: NODEV after polling detection
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3160023AS Rev: 3.05
Type: Direct-Access ANSI SCSI revision: 05
Thanks,
David
>
> If not, that would justify fast-forwarding the #sx4 branch into 2.6.30
> (with your fixes, obviously)...
>
> Thanks,
>
> Jeff
>
>
>
>
next prev parent reply other threads:[~2009-05-14 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 23:02 [PATCH #sx4] sata_sx4: fixup interrupt handling David Milburn
2009-05-13 23:26 ` Jeff Garzik
2009-05-13 23:39 ` David Milburn
2009-05-13 23:27 ` Jeff Garzik
2009-05-13 23:42 ` David Milburn
2009-05-14 14:07 ` David Milburn [this message]
2009-05-15 18:08 ` 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=4A0C2598.9090503@redhat.com \
--to=dmilburn@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=tj@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).