From: Albert Lee <albertcc@tw.ibm.com>
To: Mark Lord <liml@rtr.ca>, Robert de Rooy <robert.de.rooy@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
albertl@mail.com, Mark Lord <mlord@pobox.com>,
Jeff Garzik <jeff@garzik.org>,
bzolnier@gmail.com, linux-pcmcia@lists.infradead.org,
linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: libata and legacy ide pcmcia failure
Date: Mon, 25 Jun 2007 12:04:44 +0800 [thread overview]
Message-ID: <467F3EDC.2060002@tw.ibm.com> (raw)
In-Reply-To: <467BCF86.8060508@rtr.ca>
Mark Lord wrote:
> Robert de Rooy wrote:
>
>>
>> I did another try with libata pcmcia support using 2.6.22-rc5 which
>> already includes the nodata polling fix, in combination with
>> disable-dev_init_param-and-setxfermode-for-CFA.patch and the
>> timing-debug.patch
>
> ...
>
>> Jun 22 13:19:44 localhost kernel: ata3.00: issuing IDENTIFY
>> Jun 22 13:19:45 localhost kernel: ata3.00: IDENTIFY complete
>> Jun 22 13:19:45 localhost kernel: ata3.00: CFA: Memory Card Adapter,
>> 20011212, max PIO1
>> Jun 22 13:19:45 localhost kernel: ata3.00: 253696 sectors, multi 0: LBA
>> Jun 22 13:19:45 localhost kernel: ata3.00: issuing IDENTIFY
>> Jun 22 13:19:45 localhost kernel: ata3.00: IDENTIFY complete
>> Jun 22 13:19:45 localhost kernel: ata3.00: configured for PIO0
>> Jun 22 13:19:45 localhost kernel: ata3: EH complete
>> Jun 22 13:19:45 localhost kernel: scsi 2:0:0:0: Direct-Access
>> ATA Memory Card Adap 2001 PQ: 0 ANSI: 5
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] 253696 512-byte
>> hardware sectors (130 MB)
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] Write Protect is off
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] Write cache:
>> disabled, read cache: enabled, doesn't support DPO or FUA
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] 253696 512-byte
>> hardware sectors (130 MB)
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] Write Protect is off
>> Jun 22 13:19:45 localhost kernel: sd 2:0:0:0: [sdb] Write cache:
>> disabled, read cache: enabled, doesn't support DPO or FUA
>> Jun 22 13:20:15 localhost kernel: sdb:<3>ata3.00: exception Emask 0x0
>> SAct 0x0 SErr 0x0 action 0x2 frozen
>> Jun 22 13:20:15 localhost kernel: ata3.00: cmd
>> 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
>> Jun 22 13:20:15 localhost kernel: res
>> 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>> Jun 22 13:20:15 localhost kernel: ata3: soft resetting port
>> Jun 22 13:20:15 localhost kernel: ata3: reset complete
>> Jun 22 13:20:15 localhost kernel: ATA: abnormal status 0x80 on port
>> 0x00014107
>> Jun 22 13:20:15 localhost kernel: ATA: abnormal status 0x80 on port
>> 0x00014107
>> Jun 22 13:20:15 localhost kernel: ATA: abnormal status 0x58 on port
>> 0x00014107
>> Jun 22 13:20:15 localhost kernel: ata3.00: issuing IDENTIFY
>> Jun 22 13:20:15 localhost kernel: ATA: abnormal status 0x58 on port
>> 0x00014107
>
> ...
>
> Mmm.. I don't know about the first failure there,
> but after that it gets into the "stuck DRQ" state
> which libata makes no attempt to handle at present.
>
It seems the pata_pcmcia driver is using IRQ driven PIO. Maybe Robert
could try the following pio_polling patch first.
--
albert
---
--- libata-dev/drivers/ata/pata_pcmcia.c~ 2007-06-12 16:44:43.000000000 +0800
+++ libata-dev/drivers/ata/pata_pcmcia.c 2007-06-25 11:53:37.000000000 +0800
@@ -299,7 +299,7 @@ next_entry:
ap->ops = &pcmcia_port_ops;
ap->pio_mask = 1; /* ISA so PIO 0 cycles */
- ap->flags |= ATA_FLAG_SLAVE_POSS;
+ ap->flags |= ATA_FLAG_SLAVE_POSS | ATA_FLAG_PIO_POLLING;
ap->ioaddr.cmd_addr = io_addr;
ap->ioaddr.altstatus_addr = ctl_addr;
ap->ioaddr.ctl_addr = ctl_addr;
next prev parent reply other threads:[~2007-06-25 4:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 18:59 libata pcmcia failure Robert de Rooy
2007-05-17 8:42 ` Robert de Rooy
2007-05-17 20:15 ` libata and legacy ide " Robert de Rooy
2007-05-20 11:31 ` Tejun Heo
2007-05-20 21:13 ` Robert de Rooy
2007-05-21 11:50 ` Tejun Heo
2007-05-21 12:37 ` Alan Cox
2007-05-21 12:42 ` Tejun Heo
2007-05-21 15:10 ` Robert de Rooy
2007-05-21 15:18 ` Tejun Heo
2007-05-21 16:11 ` Robert de Rooy
2007-05-21 16:22 ` Tejun Heo
2007-05-21 17:16 ` Robert de Rooy
2007-05-21 21:12 ` Jeff Garzik
2007-05-22 19:37 ` Robert de Rooy
2007-05-23 14:02 ` Alan Cox
2007-05-23 18:47 ` Robert de Rooy
2007-06-06 20:27 ` Robert de Rooy
2007-06-07 7:28 ` Tejun Heo
2007-06-07 19:22 ` Robert de Rooy
2007-06-08 7:10 ` Tejun Heo
2007-06-08 12:46 ` Mark Lord
2007-06-08 22:06 ` Robert de Rooy
2007-06-08 22:11 ` Mark Lord
2007-06-10 1:01 ` Robert de Rooy
2007-06-10 20:46 ` Mark Lord
[not found] ` <466C723C.6000300@gmail.com>
[not found] ` <20070610221322.GA18196@flint.arm.linux.org.uk>
[not found] ` <466C7A9F.1080700@rtr.ca>
2007-06-11 22:36 ` Robert de Rooy
2007-06-11 22:40 ` Mark Lord
2007-06-12 3:24 ` Tejun Heo
2007-06-13 1:36 ` Albert Lee
2007-06-14 9:39 ` Tejun Heo
2007-06-22 11:51 ` Robert de Rooy
2007-06-22 13:32 ` Mark Lord
2007-06-25 4:04 ` Albert Lee [this message]
2007-06-25 9:31 ` Robert de Rooy
2007-06-25 10:15 ` 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=467F3EDC.2060002@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=mlord@pobox.com \
--cc=robert.de.rooy@gmail.com \
/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).