I am closing this bug now for several reasons. First, there does not seem to be
much activity anymore. The behavior seems acceptable with newer kernels. But
for Hardy it would be just too intrusive and risky to try to backport the newer
code in general. The patch Renato pointed out already is more than could be
done for a stable update. Although the problem i very annoying, it is not
critical enough to take the risk. This is sadly the truth. If someone can
pinpoint a single change by bisecting, maybe. Still that would depend on the
change and what effects might get introduced by reverting that.
So those who have to or want to stay with Hardy, a few generic thoughts. Try to
find out whether unloading certain modules helps to reduce the drain. Guess
this is simpler to test using hibernation as the pm-tools have support for
that. If a certain set of modules is found, this could be used to write a init
script to be run on shutdown.
Check whether "cat /proc/acpi/wakeup" has entries for S5 (though I do not think
there are). Should there be one enabled it can be turned of by calling "echo
'<device> disabled' >/proc/acpi/wakeup" as root.
There might also be the RTC being kept active (in theory to cause the system to
be woken at a certain date/time). I have not been able to test this but heard
that you could get it properly disabled by setting the alarm to go off manually.
Final note: even as I close this now, I someone still got that issue with
Jaunty (or whatever the current release is) please reopen the bug saying so.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
Toshiba laptop battery is drained while shut down
https://bugs.launchpad.net/bugs/110784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
