From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
IDE Linux <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>
Subject: Re: [PATCH 2/3] libata - PIO error handling fix
Date: Fri, 17 Dec 2004 20:42:48 +0100 [thread overview]
Message-ID: <58cb370e041217114221f774f5@mail.gmail.com> (raw)
In-Reply-To: <003901c4e28b$95c00f20$f17a4109@tw.ibm.com>
On Wed, 15 Dec 2004 17:50:59 +0800, Albert Lee <albertcc@tw.ibm.com> wrote:
> Hi, Jeff:
>
> Tested burning CD-RW with libata-dev-2.6 and cdrecord:
> 1. ATAPI DMA mode - tested OK
> 2. ATAPI PIO mode - test failed when cdrecord finishes burning and issues MODE_SELECT to the device.
>
> After checking the log, it showed that MODE_SELECT caused ata_pio_complete() to return error.
> However, the error is not handled by ata_pio_task().
>
> Attached please find the patch for ata_pio_task() error handling for your review.
> (The patch is against the libata-dev-2.6 tree. )
>
> Changes in the patch:
> 1. End the PIO task when PIO_ST_IDLE state is entered
> 2. End the PIO task after PIO_ST_TMOUT and PIO_ST_ERR state handled by ata_pio_error()
> 3. Remove the first "if" statement to handle the error condition returned from
> ata_pio_block(), ata_pio_complete() and ata_pio_poll().
Jeff, 3. is the same issue + fix that was reported earlier by Tim.
It seems that we have both somehow forgot about it. :-|
> Change #2 is not so necessary since ata_pio_error() will put the cmd to PIO_ST_IDLE state
> after the error condition is handled. The change just saves a function call to queue_work().
>
> Tested OK on on my machine with pdc20275 and ASUS CD-RW drive.
Patch looks fine for me.
Bartlomiej
prev parent reply other threads:[~2004-12-17 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 9:50 [PATCH 2/3] libata - PIO error handling fix Albert Lee
2004-12-17 19:42 ` Bartlomiej Zolnierkiewicz [this message]
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=58cb370e041217114221f774f5@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=albertcc@tw.ibm.com \
--cc=dwm@maxeymade.com \
--cc=jgarzik@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.