linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Dillow <dave@thedillows.org>
To: Scott McDermott <vaxerdec@frontiernet.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21: kernel BUG at ide-iops.c:1262!
Date: 24 Jun 2003 23:54:52 -0400	[thread overview]
Message-ID: <1056513292.3885.2.camel@ori.thedillows.org> (raw)
In-Reply-To: <20030624204828.I30001@newbox.localdomain>

On Tue, 2003-06-24 at 20:48, Scott McDermott wrote:
> David Dillow on Tue 24/06 18:19 -0400:
> > I've found a completely repeatable BUG/panic in 2.4.21
> > (final). The kernel BUGS and then panics in an interrupt
> > while beginning to burn a DVD+R. I get the following in
> > the logs, then the BUG/panic decoded at the end of this
> > message:
> 
> There were recent threads about this, and a Bugzilla bug 829
> I think.  

Doh! Missed those, and my quick search didn't hit. Found one after your
message, though.

> Try killing magicdev.

I thought I had, but upon checking, it was still kicking. Killing it
allows the burn to complete uninterrupted.

I'll test patches to kill the kernel BUG, but I'm happy to be able to
burn without a reboot again.

Dave

  reply	other threads:[~2003-06-25  3:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 22:19 2.4.21: kernel BUG at ide-iops.c:1262! David Dillow
2003-06-25  0:48 ` Scott McDermott
2003-06-25  3:54   ` David Dillow [this message]
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

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=1056513292.3885.2.camel@ori.thedillows.org \
    --to=dave@thedillows.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vaxerdec@frontiernet.net \
    /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;
as well as URLs for NNTP newsgroup(s).