From: "pHilipp Zabel" <philipp.zabel@gmail.com>
To: "Pierre Ossman" <drzeus@drzeus.cx>
Cc: rmk+lkml@arm.linux.org.uk,
"Pierre Ossman" <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Use own work queue
Date: Sat, 7 Oct 2006 16:17:09 +0200 [thread overview]
Message-ID: <74d0deb30610070717k17079940ybedbf94dc8af8460@mail.gmail.com> (raw)
In-Reply-To: <20061001124240.16996.34557.stgit@poseidon.drzeus.cx>
Hi,
On 10/1/06, Pierre Ossman <drzeus@drzeus.cx> wrote:
> The MMC layer uses the standard work queue for doing card detection. As
> this queue is shared with other crucial subsystems, the effects of a long
> (and perhaps buggy) detection can cause the system to be unusable. E.g. the
> keyboard stops working while the detection routine is running.
>
> The solution is to add a specific mmc work queue to run the detection code
> in. This is similar to how other subsystems handle detection (a full
> kernel thread is the most common theme).
>
> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
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?
regards
Philipp
next prev parent reply other threads:[~2006-10-07 14:17 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 [this message]
2006-10-09 21:04 ` Pierre Ossman
2006-10-13 7:56 ` Russell King
2006-10-15 9:40 ` pHilipp Zabel
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=74d0deb30610070717k17079940ybedbf94dc8af8460@mail.gmail.com \
--to=philipp.zabel@gmail.com \
--cc=drzeus-list@drzeus.cx \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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®