Thibault Manlay wrote: [...] > I will do this sometime tomorrow but I think this may take a while :-)
Thanks! > I have a friend with the same hardware as me, although he is running > stable I think it would be pertinent trying a recent kernel on his > laptop even if I'm pretty sure of the result. > > Btw, would a debug of APIC/LAPIC informations at boot be useful here? > (kernel parameters "apic=debug show_lapic=all") In that direction, the most useful things might be: 1. Report this upstream at <http://bugzilla.kernel.org/>, product ACPI and let us know the bug number so we can move to there. :) 2. Run acpidump and attach its output to the upstream bug. 3. Enable CONFIG_ACPI_DEBUG (make nconfig → Power Management and ACPI options → ACPI Support → Debug Statements) and run something like echo _LID >/sys/module/acpi/parameters/trace_method_name echo 0xffffffff >/sys/module/acpi/parameters/trace_debug_layer echo 0xffffffff >/sys/module/acpi/parameters/trace_debug_level echo 1 >/sys/module/acpi/parameters/trace_state grep . /proc/acpi/button/lid/LID*/state (see Documentation/acpi/method-tracing.txt for details). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
