From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel 2.6-test5 rmmod: kernel NULL pointer dereference
Date: 29 Sep 2003 21:52:16 GMT [thread overview]
Message-ID: <bla9ig$483$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 35776.10.0.0.50.1064747073.squirrel@mail.hackaholic.org
In article <35776.10.0.0.50.1064747073.squirrel@mail.hackaholic.org>,
detach <detach@hackaholic.org> wrote:
| Hello,
|
| I hope I'm using the right method to reporting this problem, I'll send it
| to the mailing list as this problem seems to be an overall kernel problem.
| No flames please :).
| Here's what happened,
| I wrote a CD so I did a modprobe ide-scsi .. then wrote the CD, now I
| wanted to check the contents of the CD, so i did rmmod ide-scsi first so
| that i could load ide-cd. Well, rmmod hung, and I checked /proc/kern.log
| on debian woody (with custom compiled linux 2.6-test5).Here's the output in /proc/kern.log:
Do you find there is any difference between the ide-cd operation and the
ide-scsi behaviour mounting /dev/scd0 (or sr0 depending on
distribution)? Redhat just uses the SCSI version, and I use SCSI on
Slackware as well most of the time (ie. when I have a burner).
It's good that you have reported a bug, but you may not need to go
through that path at all. As noted, supposedly fixed, although I haven't
built test6 yet.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-09-29 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 11:04 PROBLEM: kernel 2.6-test5 rmmod: kernel NULL pointer dereference detach
2003-09-28 11:15 ` Rudo Thomas
2003-09-29 21:58 ` bill davidsen
2003-09-28 17:07 ` Mike Christie
2003-09-29 21:52 ` bill davidsen [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='bla9ig$483$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.