Hi Tim,
Since my last update to this bug I've started again with a fresh install
of Feisty. I did a complete update before running this experiment so I
ought to have the latest of everything.
Following the advice in KernelSuspendDebugging, I attempted to
suspend/resume three times. Each time, I got a different message in
'dmesg'.
First attempt:
[ 10.487581] Magic number: 11:940:953
[ 10.487622] hash matches device ttya8
[ 10.487768] hash matches device ptyza
Second attempt:
[ 10.257222] Magic number: 11:119:46
[ 10.257233] hash matches device ttyef
Third attempt:
[ 9.658558] Magic number: 11:222:147
[ 9.658700] hash matches device ttyp1
However, I'm not sure if this is working properly, as, even when I'm not
connected to the network, when I start up again the laptop still seems
to know the correct time. Shouldn't pm_trace be doing something to mess
up the clock? If my clock is still correct does that mean that it's not
working right?
--
Failure to resume after suspend: Toshiba Portege 4010
https://launchpad.net/bugs/81548
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
