From: Alan <alan@clueserver.org>
To: Jens Axboe <axboe@suse.de>
Cc: David Ford <david+challenge-response@blue-labs.org>,
linux-kernel@vger.kernel.org,
Mans Matulewicz <cybermans@xs4all.nl>
Subject: Re: ide-cdrom / atapi burning bug - 2.6.1
Date: Sun, 01 Feb 2004 00:24:26 -0800 [thread overview]
Message-ID: <1075623865.26031.9.camel@zontar.clueserver.org> (raw)
In-Reply-To: <20040131184923.GD11683@suse.de>
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.)
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.
--
"Push that big, big granite sphere way up there from way down here!
Gasp and sweat and pant and wheeze! Uh-oh! Feel momentum cease!
Watch it tumble down and then roll the boulder up again!"
- The story of Sisyphus by Dr. Zeus in Frazz 12/18/2003
next prev parent reply other threads:[~2004-02-01 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 1:05 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 [this message]
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=1075623865.26031.9.camel@zontar.clueserver.org \
--to=alan@clueserver.org \
--cc=axboe@suse.de \
--cc=cybermans@xs4all.nl \
--cc=david+challenge-response@blue-labs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®