Eric Lavarde wrote:
> I'm surely not experienced in these topics, but I thought that there
> should be no difference for the BIOS / ACPI between a pure shutdown
> and a suspend to disk.
Nah, they are different. Suspend to disk happens with ACPI
cooperation.
[...]
> Let me know if I can test / do anything further to solve the issue,
It's possible your machine only supports wake from S4 and not S5, in
which case the best bet would be to get your (out-of-tree?) driver
to suspend to disk sanely. By the way, has there been any effort to
get that out-of-tree driver merged upstream? Please file a bug
describing the missing functionality it provides, and I can try
working on that.
All that said, I see no reason _in principle_ that a machine that can
wake from S4 should not be able to wake from S5. It might be possible
to debug this as an ACPI or RTC issue. Please test 3.2-rc7 from
experimental without any out-of-tree drivers, and provide:
i. full "dmesg" output from booting, setting the wakeup timer,
hibernating with "echo disk >/sys/power/state", and waking up
ii. information about what happens if you instead boot, set the wakeup
time, shutdown with "shutdown -h now", and wake up
Also, when you set the wakeup timer, is it visible from the CMOS menus?
If it is, that might help in comparing what happens in cases (i)
and (ii).
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120114163310.GA27850@burratino
