From: "pHilipp Zabel" <philipp.zabel@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Use own work queue
Date: Sun, 15 Oct 2006 11:40:31 +0200 [thread overview]
Message-ID: <74d0deb30610150240y16d6ea92mc96705576b8f0824@mail.gmail.com> (raw)
In-Reply-To: <20061013075626.GB28654@flint.arm.linux.org.uk>
On 10/13/06, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> On Mon, Oct 09, 2006 at 11:04:59PM +0200, Pierre Ossman wrote:
> > pHilipp Zabel wrote:
> > >
> > > This patch makes pxamci stop working for me on a HTC Magician (PXA272).
> > > Switching from 2.6.18 to 2.6.19-rc1 I got a kernel panic:
> > >
> > > mmc0: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0
> > > PXAMCI: clkrt = 0 cmdat = 0
> > > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0)
> > > Please append a correct "root=" boot option
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(0,0)
> > >
> > > After removing this patch from 2.6.19-rc1, everything is working again.
> > > Are there any changes to pxamci.c needed to be compatible with it?
> > >
> >
> > No, the drivers shouldn't be affected. As this is a root device, my
> > guess would be that you have a race in your bootup that is causing problem.
>
> The problem is likely that the boot is continuing in parallel with
> detecting the card, because the card detection is running in its own
> separate thread. Meanwhile, the init thread is trying to read from
> the as-yet missing root device and erroring out.
Thanks, I can work around this by using the rootdelay kernel parameter.
So does that mean this is the expected behavior, or should I do anything
in the bootup sequence to make the init process wait for mmc detection?
regards
Philipp
next prev parent reply other threads:[~2006-10-15 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 12:42 Pierre Ossman
2006-10-07 14:17 ` pHilipp Zabel
2006-10-09 21:04 ` Pierre Ossman
2006-10-13 7:56 ` Russell King
2006-10-15 9:40 ` pHilipp Zabel [this message]
2006-10-15 15:38 ` Russell King
2006-10-22 9:22 ` Pierre Ossman
2006-10-15 19:58 ` Pierre Ossman
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=74d0deb30610150240y16d6ea92mc96705576b8f0824@mail.gmail.com \
--to=philipp.zabel@gmail.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 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®