All of lore.kernel.org
 help / color / mirror / Atom feed
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:19:58 +0200	[thread overview]
Message-ID: <20040429061956.GA3558@suse.de> (raw)
In-Reply-To: <20040428221334.GA22404@taniwha.stupidest.org>

On Wed, Apr 28 2004, Chris Wedgwood wrote:
> On Wed, Apr 28, 2004 at 10:09:54PM +0200, Jens Axboe wrote:
> 
> > So it just helped me unearth a different problem :-). There
> > certainly is a bug here, it looks like it's hardware though (see the
> > above description). ide-cd just needs to have it's SYNC_CACHE
> > retries limited, then the kernel should at least recover.
> 
> I see cache flushes also go mute and hang forwever.  I think ideally
> we need to hack the IDE layer to have sane timeouts or something
> perhaps?

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.

-- 
Jens Axboe


  reply	other threads:[~2004-04-29  6:20 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 [this message]
2004-04-29  6:24               ` Chris Wedgwood
2004-04-29  6:29                 ` Jens Axboe
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=20040429061956.GA3558@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.