On Mon, 4 Apr 2011, Andrei Warkentin wrote:
On Wed, Mar 30, 2011 at 5:52 AM, Frank Hofmann <[email protected]> wrote:
Hi linux-mmc'ers,
(have originally posted this to linux-pm, got suggested I ask here as well)
I'm encountering the following deadlock:
[ mmcqd vs mmc_pm_notify ]
Hi Frank,
I was able to reproduce it on linux-next. No need for rootfs on
mmcblk, and a "echo mem > /sys/power/state" is sufficient to trigger
the issue.
I am looking into it.
Thanks,
A
Thanks Andrei.
Missed to make it clear in the original email that disabling the notifier
via CONFIG_MMC_UNSAFE_RESUME stops it from occurring.
Also found that simply reverting _part_ of the commit isn't helping
because the deadlock just moves ... to mmc_suspend_host() eventually also
ending up in del_gendisk(), and things are identical from there.
FrankH.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
