From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Isaacson <adi@hexapodia.org>,
linux-kernel@vger.kernel.org, rjw@sisk.pl
Subject: Re: 2.6.25-mm1: kmmcd NULL pointer dereference at klist_del+0xe/0x30
Date: Mon, 12 May 2008 19:10:41 +0200 [thread overview]
Message-ID: <20080512191041.397f9ccf@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080509164738.2e0af511.akpm@linux-foundation.org>
On Fri, 9 May 2008 16:47:38 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 9 May 2008 10:19:56 -0700
> Andy Isaacson <adi@hexapodia.org> wrote:
>
> > Got this twice with 2.6.25-mm1 on my Thinkpad X40, AData 16GB SDHC card
> > in mmc0 but no filesystem mounted. I think the oops happened at
> > suspend/resume time. Previous kernel was 2.6.25-rc5-mm1 which didn't
> > exhibit this problem across multiple suspend-resume cycles.
> >
> > Complete logs and pretty much everything else you could want at
> > http://web.hexapodia.org/~adi/bobble/bobble_2.6.25-mm1-dirty_20080509100634/
> >
> > [104375.816331] BUG: unable to handle kernel NULL pointer dereference at 0000000c
> > [104375.816338] IP: [<c02d86ce>] klist_del+0xe/0x30
>
> This could be one of those nasty situations where one driver leaves a mess
> behind it and then another driver later comes along and trips over that
> mess.
>
There were some problems with removing devices during suspend (which
the MMC layer does), but AFAIK those patches were backed out and were
only supposed to come back in a form that allowed such usage. Rafael
should have the most correct information on that subject.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2008-05-12 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 17:19 Andy Isaacson
2008-05-09 23:47 ` Andrew Morton
2008-05-12 17:10 ` Pierre Ossman [this message]
2008-05-12 19:43 ` Rafael J. Wysocki
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=20080512191041.397f9ccf@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=adi@hexapodia.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 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®