ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
Bug #43661 reported by
Mark Shuttleworth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.15 (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
linux-source-2.6.17 (Baltix) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.17 (Ubuntu) |
Fix Released
|
Undecided
|
Ben Collins | ||
util-linux (Debian) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Dapper seems unable to read or set my RTC on an IBM/Lenovo X60 thinkpad.
The BIOS shows the hardware clock to be several hours different to the
Linux clock. When the network comes up, the screensaver appears to kick
in because the ntpdate moves the system clock to bring it up to date.
There are other symptoms:
peregrine% sudo
hwclock ~
select() to /dev/rtc to wait for clock tick timed out
affects /distros/ubuntu
:
I can confirm this on an Intel dual core Pentium. I synchronized my clock with an NTP server on Friday, and started up NTP, which should have kept it in sync. I rebooted today (Sunday) to install a video card, and my clock is several hours wrong again - I suspect because it got set from the hwclock, and NTP won't correct it by such a big jump. I can't query the hwclock, though, with the same error as above:
$ sudo hwclock
select() to /dev/rtc to wait for clock tick timed out