From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Cc: Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>,
Rudo Thomas <rudo@internet.sk>
Subject: Re: kernel oops when burning CDs
Date: Wed, 06 Jun 2001 22:11:39 -0400 [thread overview]
Message-ID: <3B1EE2DB.A0AE01FE@torque.net> (raw)
Tachino wrote:
> At Mon, 4 Jun 2001 22:43:30 +0100 (BST),
> Alan Cox wrote:
> >
> > > I get an ooops and immediate kernel panic when I break (CTRL-C) cdrecord. I
> > > can reproduce it anytime. I use 2.4.5-ac series. Obviously, Linus' 2.4.5 is
> > > fine.
> > > I know, I know. I was supposed to make a serios oops report, BUT I wasn't
> >
> > Write down the EIP and the call trace then look them up in System.map. Also
> > include the hardware details. The -ac tree has a newer version of the scsi
> > generic code. It fixes some oopses but in your case it apparently added a new
> > failure case
>
> Oops occures in SG driver. This patch fixes the problem.
[patch snipped. It looks fine]
Tachino,
Thanks for the patch. Alan Cox has incorporated it in lk 2.4.5-ac9 .
The problem only occurs when the sg driver is built in. [I do my
testing with sg built as a module.]
Currently sg version 3.1.18 is in the ac tree while the previous
version (3.1.17) is in the main branch. The code that oopsed is
there to temporarily bump the sg module count to inhibit rmmod
(and/or autoclean) until all SCSI commands on that device are
finished.
Doug Gilbert
next reply other threads:[~2001-06-07 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 2:11 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-04 20:46 kernel oops when burning CDs Rudo Thomas
2001-06-04 21:43 ` Alan Cox
2001-06-05 1:33 ` Tachino Nobuhiro
2001-06-05 4:19 ` Rudo Thomas
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=3B1EE2DB.A0AE01FE@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rudo@internet.sk \
--cc=tachino@open.nm.fujitsu.co.jp \
/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