From: Jens Axboe <axboe@suse.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Kenneth Johansson <ken@kenjo.org>,
Moritz Muehlenhoff <jmm@informatik.uni-bremen.de>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] DVD writing in 2.6.6-rc2
Date: Thu, 29 Apr 2004 08:29:50 +0200 [thread overview]
Message-ID: <20040429062949.GB3558@suse.de> (raw)
In-Reply-To: <20040429062436.GA6507@taniwha.stupidest.org>
On Wed, Apr 28 2004, Chris Wedgwood wrote:
> On Thu, Apr 29, 2004 at 08:19:58AM +0200, Jens Axboe wrote:
>
> > Yeah, with 'retries' I mean waiting retries. The command does expire
> > and ide-cd notices it just doesn't put an upper bound on how long it
> > waits. A minute or so should suffice, unless the caller specifies
> > otherwise.
>
> Can we poke the IDE drive is it's hung or reset it in these cases? I
> wonder more in the general case where I've had to reboot because the
> burner went nuts for some reason...
Drive needs to be reset. Something like this should be all that's
needed.
===== drivers/ide/ide-cd.c 1.81 vs edited =====
--- 1.81/drivers/ide/ide-cd.c Mon Apr 26 22:56:10 2004
+++ edited/drivers/ide/ide-cd.c Thu Apr 29 08:29:07 2004
@@ -844,7 +844,6 @@
case GPCMD_FORMAT_UNIT:
case GPCMD_RESERVE_RZONE_TRACK:
case GPCMD_CLOSE_TRACK:
- case GPCMD_FLUSH_CACHE:
wait = ATAPI_WAIT_PC;
break;
default:
--
Jens Axboe
next prev parent reply other threads:[~2004-04-29 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 17:59 [BUG] DVD writing in 2.6.6-rc2 Kenneth Johansson
2004-04-27 18:36 ` Jens Axboe
2004-04-27 22:16 ` Moritz Muehlenhoff
2004-04-28 11:30 ` Jens Axboe
2004-04-28 18:29 ` Kenneth Johansson
2004-04-28 20:09 ` Jens Axboe
2004-04-28 22:13 ` Chris Wedgwood
2004-04-29 6:19 ` Jens Axboe
2004-04-29 6:24 ` Chris Wedgwood
2004-04-29 6:29 ` Jens Axboe [this message]
2004-04-28 19:20 ` Moritz Muehlenhoff
2004-04-27 22:24 ` Panagiotis Papadakos
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=20040429062949.GB3558@suse.de \
--to=axboe@suse.de \
--cc=cw@f00f.org \
--cc=jmm@informatik.uni-bremen.de \
--cc=ken@kenjo.org \
--cc=linux-kernel@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.