From: Jens Axboe <axboe@suse.de>
To: Alan <alan@clueserver.org>
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:27:42 +0100 [thread overview]
Message-ID: <20040201152742.GH11683@suse.de> (raw)
In-Reply-To: <1075623865.26031.9.camel@zontar.clueserver.org>
On Sun, Feb 01 2004, Alan wrote:
> On Sat, 2004-01-31 at 10:49, 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.
>
> I have seen the problem as well.
>
> It is not just processes using the IDE. Everything will pause for a
> second or two. (Which causes grief with streaming audio running at the
> same time.)
One process can easily stall the other, if they end up waiting on some
resource. Might not always happen, but easily can.
> Even more annoying is that it does not always occur. I have not tried
> tracking down where the kernel is getting hung up at that moment since
> it has been fairly intermittent for me.
There's not much you can do about it - you may want to try -immed as
mentioned earlier in this thread.
--
Jens Axboe
prev parent reply other threads:[~2004-02-01 15:28 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
2004-02-01 8:24 ` Alan
2004-02-01 15:27 ` Jens Axboe [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=20040201152742.GH11683@suse.de \
--to=axboe@suse.de \
--cc=alan@clueserver.org \
--cc=cybermans@xs4all.nl \
--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