From: Scott McDermott <vaxerdec@frontiernet.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21: kernel BUG at ide-iops.c:1262!
Date: Wed, 25 Jun 2003 17:37:24 -0400 [thread overview]
Message-ID: <20030625173724.A9146@newbox.localdomain> (raw)
In-Reply-To: <20030625212007.GV3710@fs.tum.de>; from bunk@fs.tum.de on Wed, Jun 25, 2003 at 11:20:07PM +0200
Adrian Bunk on Wed 25/06 23:20 +0200:
> > > There were recent threads about this, and a Bugzilla
> > > bug 829 I think. Try killing magicdev.
> >
> > Okay, I'll ask a LKML-newbie question. Bugzilla says
> > "Linux 2.5 kernel bugs only at this time"... Does that
> > mean this bug won't be fixed in 2.4, or just that the
> > fix will be written for 2.5 and then backported to 2.4?
>
> The Bugzilla tracks only 2.5 bugs.
>
> Whether it will be fixed in 2.4 or a fix will be
> backported to 2.4 is beyond the scope of the Bugzilla (but
> of course Bugzilla does not affect how kernel developers
> write and submit fixes).
it tracks 2.5 but I think the bug is the same; it appears
the relevant code has changed but I think the root issue
probably is the same (ide-scsi reset error handling causing
kernel to crash). The bug submitter for the original bug
said he gets the same behavior on 2.4, but he didn't yet
respond as to whether killing magicdev fixes his problem.
Maybe they're different problems, but they appear related.
prev parent reply other threads:[~2003-06-25 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 22:19 David Dillow
2003-06-25 0:48 ` Scott McDermott
2003-06-25 3:54 ` David Dillow
2003-06-25 12:00 ` Alan Cox
2003-06-25 22:47 ` Scott McDermott
2003-06-25 22:49 ` Alan Cox
[not found] ` <1056557323.1444.4.camel@dhcp22.swansea.linux.org.uk>
2003-06-26 3:17 ` David Dillow
2003-06-26 21:34 ` Alan Cox
2003-06-27 2:58 ` David Dillow
2003-06-25 7:42 ` Roland Mas
2003-06-25 21:20 ` Adrian Bunk
2003-06-25 21:37 ` Scott McDermott [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=20030625173724.A9146@newbox.localdomain \
--to=vaxerdec@frontiernet.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
all inboxes | Powered by JetHome®