To work this problem, we'll follow standard ACPI debugging procedures
([1], [2]). First, please confirm that you have up-to-date BIOS, and
update the report with the output of "uname -a".
Next, please attach the output of the following commands:
sudo lspci -vv
sudo lspci -vvn
sudo dmidecode
(Please be sure to use sudo, root privileges are required to obtain the
necessary information. Please attach one file per command, please do not
compress the output, please do not add the output in-line, and please do
not attempt to email in the attachments - they have to be added to the
report within Launchpad.)
It might also be useful if you could try the procedures described in
[2]; there may be a driver breaking under Feisty.
As an aside, ntp is likely a red herring: If the time is correct before
the machine suspends, then it should be correct upon resume, based on a
reading of the hardware clock: NTP is used to ensure that the system
time matches "real time", the system itself is responsible for tracking
the passage of time. If you're curious to learn more, try the following
from the command line:
man hwclock
man rtc
man 7 time
Note: These are not light reading! (But they will definitely help
explain the responsibilities of the hardware clock, the system clock,
and ntp.)
Thanks!
[1] https://wiki.ubuntu.com/DebuggingACPI
[2] https://wiki.ubuntu.com/DebuggingKernelSuspend
** Changed in: acpi (Ubuntu)
Assignee: (unassigned) => Peter Whittaker
Status: Unconfirmed => Needs Info
--
after resuming from suspend the system time is wrong
https://bugs.launchpad.net/bugs/107445
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
