Skip to contentSkip to conversation

Spurious power button event on resume from hibernate

DISCUSSION Francis Russell 1 participant 2 messages May 14, 2009 – May 18, 2009 ACPI

lore
Share & tools
lore
#0 lore raw

Hi all,

I have a Samsung R560 laptop running amd64 Debian testing with a 2.6.29.3 kernel compiled from vanilla sources. Upon resume from hibernate, it appears that the OS receives a power button event that causes the system to shut down. I've verified this the best I can by killing acpid then watching the output of /proc/acpi/event during hibernate (triggered by writing 'disk' to /sys/power/state).

This problem looked very similar to that discussed in another Bugzilla entry (http://bugzilla.kernel.org/show_bug.cgi?id=6612) so I had I extended the changes made by the patch in the obvious way to the S4 state but it made no difference. Is this something the kernel should be handling? How can I debug this further?

Many thanks,

Francis

#1 lore raw

Well, it's been a little while. Anyone have any ideas on the below? Assuming it's related to the bug previously mentioned
(http://bugzilla.kernel.org/show_bug.cgi?id=6612) which it might not be at all, it looks like the accepted patch in the bug report is clearing an ACPI event which should never get generated in the first place? If so, could the same thing be happening here?

Quoted 12 lines

I have a Samsung R560 laptop running amd64 Debian testing with a 2.6.29.3 kernel compiled from vanilla sources. Upon resume from hibernate, it appears that the OS receives a power button event that causes the system to shut down. I've verified this the best I can by killing acpid then watching the output of /proc/acpi/event during hibernate (triggered by writing 'disk' to /sys/power/state).

This problem looked very similar to that discussed in another Bugzilla entry (http://bugzilla.kernel.org/show_bug.cgi?id=6612) so I had I extended the changes made by the patch in the obvious way to the S4 state but it made no difference. Is this something the kernel should be handling? How can I debug this further?