From: Jens Axboe <axboe@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: 2.5.64-mm6: oops in elv_remove_request
Date: Mon, 24 Mar 2003 14:14:28 +0100 [thread overview]
Message-ID: <20030324131428.GF2371@suse.de> (raw)
In-Reply-To: <1047920186.1246.32.camel@ixodes.goop.org>
On Mon, Mar 17 2003, Jeremy Fitzhardinge wrote:
> On Mon, 2003-03-17 at 00:05, Jens Axboe wrote:
> > On Sat, Mar 15 2003, Jeremy Fitzhardinge wrote:
> > > On Sat, 2003-03-15 at 00:15, Jens Axboe wrote:
> > > > I can reliably crash the box with SG_IO -> ide-cd here, so I'm hoping
> > > > there's a connection. Need to move it to a box where nmi watchdog
> > > > actually works...
> > >
> > > And wouldn't you know it - with -mm7 it seems to be working fine...
> > ^^
> > What is 'it'?
>
> Sorry: I meant "cdrecord dev=/dev/hdc -checkdrive" returns correct
> "supported modes".
>
> I was wrong, however: it is still broken. Sometimes it will return
> version 2/format 2 results time after time (with supported modes), but
> then I leave it for a while and it reverts to returning 0/1 results with
> no supported modes. There doesn't seem to be any rhyme or reason about
> it: the "put a disc in and it works" trick doesn't work any more.
>
> This is with 2.5.64-mm8. What other details would help? strace output
> of cdrecord?
Does this patch help at all? At least it solves the hard hangs (machine
double faults) in some circumstances. Linus, please apply. It may not be
this bug, but it's at least one bug.
===== drivers/ide/ide-cd.c 1.40 vs edited =====
--- 1.40/drivers/ide/ide-cd.c Fri Mar 14 01:49:24 2003
+++ edited/drivers/ide/ide-cd.c Mon Mar 24 14:08:15 2003
@@ -1749,8 +1749,8 @@
/*
* pad, if necessary
*/
- if (len) {
- while (len) {
+ if (len > 0) {
+ while (len > 0) {
int pad = 0;
xferfunc(drive, &pad, sizeof(pad));
--
Jens Axboe
next prev parent reply other threads:[~2003-03-24 13:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 17:22 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Jeremy Fitzhardinge
2003-03-13 17:45 ` Jeremy Fitzhardinge
2003-03-13 17:54 ` Jens Axboe
2003-03-13 18:04 ` Jeremy Fitzhardinge
2003-03-13 19:02 ` Jens Axboe
2003-03-14 9:24 ` 2.5.64-mm6: oops in elv_remove_request Jeremy Fitzhardinge
2003-03-14 10:42 ` Jens Axboe
2003-03-14 10:06 ` Jeremy Fitzhardinge
2003-03-14 10:31 ` Jeremy Fitzhardinge
2003-03-14 11:37 ` Jens Axboe
2003-03-14 17:59 ` Jeremy Fitzhardinge
2003-03-14 18:07 ` Jens Axboe
2003-03-14 22:19 ` Jeremy Fitzhardinge
2003-03-15 8:15 ` Jens Axboe
2003-03-16 2:54 ` Jeremy Fitzhardinge
2003-03-17 8:05 ` Jens Axboe
2003-03-17 16:56 ` Jeremy Fitzhardinge
2003-03-24 13:14 ` Jens Axboe [this message]
2003-03-14 20:33 ` Jens Axboe
2003-03-14 22:15 ` Jeremy Fitzhardinge
2003-03-15 8:15 ` Jens Axboe
2003-03-13 20:52 ` 2.5.64-mm6: kernel BUG at kernel/timer.c:155! Aravind
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=20030324131428.GF2371@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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