public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Daniel Pittman <daniel@rimspace.net>
Cc: linux-kernel@vger.kernel.org, Mans Matulewicz <cybermans@xs4all.nl>
Subject: Re: ide-cdrom / atapi burning bug - 2.6.1
Date: Sun, 1 Feb 2004 16:25:24 +0100	[thread overview]
Message-ID: <20040201152524.GG11683@suse.de> (raw)
In-Reply-To: <87r7xfy8gb.fsf@enki.rimspace.net>

On Sun, Feb 01 2004, Daniel Pittman wrote:
> On Sat, 31 Jan 2004, Jens Axboe wrote:
> > On Sat, Jan 31 2004, David Ford wrote:
> >> I don't have an RW, but when my cdrom fixates, it stalls everything 
> >> while it's fixating.  I have an nForce chipset.  (2.6.x)
> > 
> > Does "everything" mean everything on that ide channel? If so, then
> > that's a hardware limitation.
> 
> My IBM A31p (Intel 845 chipset) had a similar problem with the CD
> burner. Using the '-immed' flag resolved the issue for me.

(Dave cut from cc, annoying auth process required to mail him)

immed will help, because it causes the command to 'release' in as close
a sense to the word as ide allows. I'm not sure if error handling works
correctly in that case?

-- 
Jens Axboe


  reply	other threads:[~2004-02-01 15:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  1:05 ide-cdrom / atapi burning bug - 2.6.1 Mans Matulewicz
2004-01-31  9:34 ` Jens Axboe
2004-01-31 10:10   ` Mans Matulewicz
2004-01-31 10:20     ` Jens Axboe
2004-01-31 10:27       ` Mans Matulewicz
2004-01-31 10:32         ` Jens Axboe
2004-01-31 16:45           ` Mans Matulewicz
2004-01-31 18:17   ` David Ford
2004-01-31 18:49     ` Jens Axboe
2004-02-01  0:00       ` Daniel Pittman
2004-02-01 15:25         ` Jens Axboe [this message]
2004-02-01  8:24       ` Alan
2004-02-01 15:27         ` Jens Axboe

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=20040201152524.GG11683@suse.de \
    --to=axboe@suse.de \
    --cc=cybermans@xs4all.nl \
    --cc=daniel@rimspace.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox