[Expired for linux-source-2.6.15 (Ubuntu) because there has been no
activity for 60 days.]
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://bugs.launchpad.net/bugs/43661
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct sub
Ben, how do you think this was fixed?
I'm on Debian using x60, and I've tried running various ubuntu kernels,
but without any change. The only thing that helped was editing the
init.d/hwclock.sh script and HWCLOCKPARS=--directisa
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed
Ben, how do you think this was fixed?
I'm on Debian using x60, and I've tried running various ubuntu kernels,
but without any change. The only thing that helped was editing the
init.d/hwclock.sh script and HWCLOCKPARS=--directisa
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed
additional info to my last comment
List of kernels I've tried
ubuntu kernels
linux-image-2.6.19-7-386, 2.6.17-10.33
linux-image-2.6.17-10-386 2.6.19-7.11
custom built
linux-image-2.6.20-rc2
debian kernels
linux-image-2.6.18-3-686 2.6.18-8
--
ThinkPad X60: select() to /dev/rtc to wait for cl
I've just teste the 2.6.20-2 ubuntu package, with same results when running
hwclock.
the bios on this laptop is latest 2.06
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://launchpad.net/bugs/43661
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Not the same bug.
** Changed in: util-linux (Debian)
Importance: Unknown => Untriaged
Bugwatch: Debian Bug tracker #277298 => None
** Changed in: util-linux (Debian)
Status: Unconfirmed => Rejected
** Also affects: linux-source-2.6.17 (Baltix)
Importance: Untriaged
Statu
Seems this is fixed in edgy.
Mark, thanks for the use of the laptop t test.
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) => Ben Collins
Status: Unconfirmed => Fix Released
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://launchpad.
I can reproduce the bug on my Dell XPS m1210 laptop. --directisa fixes it
though it still consumes quite a bit of CPU and time while it works.
And in my case, `hwclock --directisa --show` gives no output.
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://launchpad.ne
** Tags added: dapper
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://launchpad.net/bugs/43661
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Interesting. I get the same results from hwclock -r and -w, with or
without --directisa. And this bug does not seem to appear on my system
any more. Is there any way to fix the system so that it knows when to
use directisa?
Mark
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed
--directisa option works for me! (IBM thinkpad x60 also).
[EMAIL PROTECTED]:/home/bar# hwclock --directisa -w
[EMAIL PROTECTED]:/home/bar# hwclock --directisa -r
Wed 12 Jul 2006 13:10:36 CEST -0.494677 seconds
lg, a
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https:/
peregrine%
hwclock~
Fri 23 Jun 2006 18:52:23 BST -0.007185 seconds
peregrine% hwclock
--directisa~
hwclock is unable to get I/O port access: the iopl(3) call failed.
Probably you need root
Can you try running "hwclock --directisa" and see if that works?
Also "dmesg | grep -i rtc" and "lsmod | grep rtc" outputs would be
useful.
Thanks
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed => Needs Info
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick t
So this is not just laptop-specific?
importance high
** Changed in: linux-source-2.6.15 (Ubuntu)
Importance: Medium => High
--
ThinkPad X60: select() to /dev/rtc to wait for clock tick timed out
https://launchpad.net/bugs/43661
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
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
15 matches
Mail list logo