> I explicitly confirmed this on top of 2.6.33.2: Thanks that makes a bit more sense.
> > 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" > > So any code enabled by CONFIG_MEMORY_HOTPLUG is the winner, presumable > somewhere in the mmc code (?). I doubt the mmc code really knows anything about memory hotplug. Must be some subtle side effect. 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. -Andi -- 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
