On Mon, May 03, 2010 at 08:47:21PM +0200, Stephan Sürken wrote: > On Sun, 2010-05-02 at 01:04 +0200, Andi Kleen wrote: > (..) > > > config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohiber:CONFIG_MEMORY_HOTPLUG=y > > > =>"bad" > > > config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohotplug:# CONFIG_MEMORY_HOTPLUG is not set > > > =>"good" > (..) > > Can send the diff of two boot logs with memory hotplug on and off? > > I wonder if you have the same memory layout in both cases. > > Attached, from the above two good/bad kernel builds; I stripped the > stamps to make it more readable. Thanks, I was hoping for a comparison between memory hotplug on and off with hibernation always off, this seems to be between memory hotplug and hibernation. Anyways looking at this log. The only significant difference I can see is that in the one case a lot of stuff including sdhci get initialized earlier. Presumably the timing is somewhat different related to the USB scanning and the memory hotadd kernel being a bit slower to boot (perhaps due to the increased printks) Perhaps this exposes some races that cause the problem. What these races are I don't know. I would suggest to check with the mmc maintainer. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
