Re: [linux-pm] intermittent suspend problem again

From: Ferenc Wagner
Date: Tue Nov 03 2009 - 06:03:28 EST

Ferenc Wagner <wferi@xxxxxxx> writes:


> So: with the new s2disk I got a freeze again after S|. After a manual
> power off and a successful resume, I switched to shutdown mode and
> hibernated again, and got the exact same freeze (apart from a slightly
> different image size). Power off, resume, switch to reboot mode,
> hibernate, and this worked. Switch back to shutdown, now that worked
> as well... Eh. In my earlier bug report I think I noted that after
> such a hibernation failure a straight shutdown didn't power off the
> computer as it otherwise does, which feels consistent with the above.


> Now something else, which may or may not be related. I supervise a
> computing farm running a very old OS: Debian Sarge. The kernel was
> somewhat newer: 2.6.24 until recently, when new machines arrived to the
> lab, which couldn't boot that 2.6.24 kernel. So I upgraded to 2.6.31,
> which works quite well, apart from one thing: halt doesn't power off the
> machines anymore. All the same under 2.6.32-rc5: they simply freeze
> after reaching halt -d -f -i -h -p in the shutdown sequence.


so now I've got three ACPI and/or PM related problems: A) and B) above
with hibernation and halt/poweroff, and the C) graphics and suspend
related described at
(which turned out to be ACPI related recently).

B) and C) are 100% reproducible, although the machines exhibiting C) are
at a different geographic location, so I have to bug a remote admin for
power switching.

A) and C) are exhibited by my laptop.

I'd be grateful for debugging tips for any of the above. While A) is
not reproducible, it happens often enough with the platform method (I
haven't got enough data with the shutdown method yet). I'm willing to
recompile kernels, read up on documentation and code and have parallel
port LEDs handy (for the laptop). But I've got no experience with ACPI
or PM, sadly. However, 2.6.32 is currently nominated as more than a
couple of distros' choice for long term stable support, so I'm willing
to invest substantial effort into fixing these issues.

If anybody has debugging tips, please share (and note if further
questions aren't welcome).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at