From: Mark Lord <liml@rtr.ca>
To: Eamonn Hamilton <EAMONN.HAMILTON@saic.com>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: problems with sata_mv and MV88SX5081 under 2.6.28, fine under 2.6.17.6
Date: Thu, 15 Jan 2009 14:37:07 -0500 [thread overview]
Message-ID: <496F9063.3080702@rtr.ca> (raw)
In-Reply-To: <496CEB3A.2090608@rtr.ca>
> Eamonn Hamilton wrote:
>> Hi Mark.
>>
>> It bisected down to the following:
>>
>> e3472cbe5c10a91c737405cd706142787736392c is first bad commit
>> commit e3472cbe5c10a91c737405cd706142787736392c
>> Author: Albert Lee <albertcc@tw.ibm.com>
>> Date: Thu Dec 7 11:37:58 2006 +0800
>>
>> libata: let ATA_FLAG_PIO_POLLING use polling pio for ATA_PROT_NODATA
>>
>> Even if ATA_FLAG_PIO_POLLING is set, libata uses irq pio for the
>> ATA_PROT_NODATA protocol.
>> This patch let ATA_FLAG_PIO_POLLING use polling pio for the
>> ATA_PROT_NODATA protocol.
>>
>> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
>> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>> ---
> ..
>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>> index 8816e30..d2e6863 100644
>> --- a/drivers/ata/libata-core.c
>> +++ b/drivers/ata/libata-core.c
>> @@ -4960,6 +4960,7 @@ unsigned int ata_qc_issue_prot(struct
>> ata_queued_cmd *qc)
>> if (ap->flags & ATA_FLAG_PIO_POLLING) {
>> switch (qc->tf.protocol) {
>> case ATA_PROT_PIO:
>> + case ATA_PROT_NODATA:
>> case ATA_PROT_ATAPI:
>> case ATA_PROT_ATAPI_NODATA:
>> qc->tf.flags |= ATA_TFLAG_POLLING;
>>
> ..
>> Now, why it dies after that, I don't know, it's one flag being added.
..
Eamonn,
Have you tried testing with the latest sata_mv fix?
This fixes interrupt problems with all 8-port sata_mv chips,
including the one you have access to.
Please give this patch a try and report back. Thanks.
The patch is against 2.6.28, but will probably apply
to several earlier kernel versions as well.
--- linux-2.6.28/drivers/ata/sata_mv.c 2009-01-13 15:57:11.000000000 -0500
+++ linux/drivers/ata/sata_mv.c 2009-01-14 16:56:38.000000000 -0500
@@ -883,7 +883,7 @@
struct mv_host_priv *hpriv = ap->host->private_data;
int hardport = mv_hardport_from_port(ap->port_no);
void __iomem *hc_mmio = mv_hc_base_from_port(
- mv_host_base(ap->host), hardport);
+ mv_host_base(ap->host), ap->port_no);
u32 hc_irq_cause, ipending;
/* clear EDMA event indicators, if any */
next prev parent reply other threads:[~2009-01-15 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 14:53 problems with sata_nv and MV88SX5081 under 2.6.28, fine under2.6.17.6 Eamonn Hamilton
2009-01-07 15:45 ` Alan Cox
2009-01-07 15:46 ` Eamonn Hamilton
2009-01-08 3:13 ` Robert Hancock
2009-01-08 10:51 ` problems with sata_nv and MV88SX5081 under 2.6.28, fineunder2.6.17.6 Eamonn Hamilton
2009-01-09 19:46 ` problems with sata_nv and MV88SX5081 under 2.6.28, fine under2.6.17.6 Mark Lord
[not found] ` <496B9130.2000708@pobox.com>
[not found] ` <D1CE94B2C9BA8C42AC5C7BBCD82D5DAE672F13@0602-its-exmb01.eu.saic.com>
[not found] ` <496BA7C5.2020802@pobox.com>
[not found] ` <D1CE94B2C9BA8C42AC5C7BBCD82D5DAE672F14@0602-its-exmb01.eu.saic.com>
[not found] ` <496BAA1F.5030802@pobox.com>
2009-01-13 17:01 ` Eamonn Hamilton
2009-01-13 19:27 ` problems with sata_mv and MV88SX5081 under 2.6.28, fine under 2.6.17.6 Mark Lord
2009-01-15 19:37 ` Mark Lord [this message]
2009-01-16 10:52 ` Eamonn Hamilton
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=496F9063.3080702@rtr.ca \
--to=liml@rtr.ca \
--cc=EAMONN.HAMILTON@saic.com \
--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).