> -----Original Message-----
> From: linux-mmc-ow...@vger.kernel.org
> [mailto:linux-mmc-ow...@vger.kernel.org] On Behalf Of Linus Walleij
> Sent: Tuesday, May 17, 2011 1:56 AM
> To: Guennadi Liakhovetski
> Cc: Chris Ball; David Strobach; linux-mmc@vger.kernel.org; Greg KH;
> ho...@verge.net.au; d...@opensource.se; Andrei Warkentin
> Subject: Re: kernel 2.6.38.6 MMC controller problem (fwd)
>
> 2011/5/16 Guennadi Liakhovetski <g.liakhovet...@gmx.de>:
> > On Mon, 16 May 2011, Chris Ball wrote:
> >> My intuition is that we should revert it now -- it's been a week since
> >> the final -rc, so you'd expect .39 to be released today, and we can
> >> always add your patch back into stable via .40-rc1 if it's not related
> >> to the crashes.
> >
> > Ok, let's revert it then. Just we have to not forget to work on this
> > problem and find a proper fix.
>
> I'm still baffled by the whole thing, the solution seems so intuitively
> correct. :-(
>
> Is there something strange in the semantics of mmc_claim_host()?
>
mmc clock gating thread may be delayed for a long time in some scenarios. Since
mmc_claim_host will be also used by other thread. I think this will possibly
happen.
But not sure the system how to treat the long time delayed.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
