From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Pierre Ossman <drzeus@drzeus.cx>,
Jens Axboe <jens.axboe@oracle.com>,
bugme-daemon@bugzilla.kernel.org, gentuu@gmail.com,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bugme-new] [Bug 9674] New: Oops during rmmod'ing modeuls sdhci, sr_mod, ricoh_mmc, mmc_core
Date: Tue, 01 Jan 2008 21:24:43 -0600 [thread overview]
Message-ID: <1199244283.3252.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20080101181026.38298e13.akpm@linux-foundation.org>
On Tue, 2008-01-01 at 18:10 -0800, Andrew Morton wrote:
> On Tue, 1 Jan 2008 14:55:45 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9674
> >
> > Summary: Oops during rmmod'ing modeuls sdhci, sr_mod, ricoh_mmc,
> > mmc_core
>
> Guys, this is a very recent regression. Could you please take a look, see
> if it's due to mmc, block or scsi changes?
There's not a lot of information to go on. The stack trace looks bogus,
so I guess the kernel is compiled without a frame pointer. However, it
does look like the initial insertion of sr_mod is going through and it
generates a command which gets into scsi_request_fn and then indirects
through a bogus queueucommand pointer.
What's the actual underlying device the cdrom is attached to?
There's no real changes to SCSI in this area from 2.6.24-rc4 ...
however, the reinsertion is suggestive, it's like the removal is
retriggering a module request for some reason.
James
next parent reply other threads:[~2008-01-02 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9674-10286@http.bugzilla.kernel.org/>
[not found] ` <20080101181026.38298e13.akpm@linux-foundation.org>
2008-01-02 3:24 ` James Bottomley [this message]
2008-01-02 12:21 ` [Bugme-new] [Bug 9674] New: Oops during rmmod'ing modeuls sdhci, sr_mod, ricoh_mmc, mmc_core Rafael J. Wysocki
2008-01-02 15:41 ` James Bottomley
2008-01-02 15:49 ` Pete Wyckoff
2008-01-02 16:33 ` James Bottomley
2008-01-02 17:14 ` [PATCH] scsi_sysfs: restore prep_fn when ULD is removed James Bottomley
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=1199244283.3252.13.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=drzeus@drzeus.cx \
--cc=gentuu@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.