Ben Hutchings wrote: > On Wed, Aug 31, 2011 at 11:08:30PM +0200, Thibault Manlay wrote:
>> Issue comes from "CONFIG_LOCKUP_DETECTOR=y" (issue disappears when >> unsetting it). >> >> But why would this option/feature "locks-up" the system? > > It doesn't. It just tells you when a process is stuck for a long > time. If the process eventually recovers, and this option is > disabled, then you might not notice. That's the theory, but if Thibault has to use the power button to reboot to recover, then something's going wrong, no? Anyway, it seems it's time to take this upstream. Thibault, could you send a summary of findings so far (i.e., what the state is like when closing the lid, problem only shows up with CONFIG_LOCKUP_DETECTOR=y, the nolapic kernel parameter works around it, whatever logs it was possible to get of what happens until the lid closes, and an acpidump) to the [email protected] list (no subscription needed, since the convention is to always reply-to-all), cc-ing this bug log? Sorry for the trouble, and good luck. Thanks, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/20110912193656.GA30915@elie
