I forgot, I'm upgraded to bios revision A08 last week.
Now I'm running the following script to force the bug happen.
while true; do
sudo /etc/init.d/hwclock.sh start;
sleep 2;
sudo /etc/init.d/hwclock.sh stop;
sleep 2;
done
...And guess, I got it, because in other term ran the following script:
~$ while true; do sudo hwclock --show; sleep 2; done
Password:
Fri 01 Sep 2006 12:39:07 AM CST -0.475796 seconds
select() to /dev/rtc to wait for clock tick timed out
select() to /dev/rtc to wait for clock tick timed out
Well, had to kill a lot of instances of hwclock that were running. I didn't know that script lauch a new instance each time.
My conclusion is, Ubuntu 6.06.1 with Linunx 2.6.17 is affected too, even using --directisa.
Hello again,
I forgot, I'm upgraded to bios revision A08 last week.
Now I'm running the following script to force the bug happen.
while true; do d/hwclock. sh start; d/hwclock. sh stop;
sudo /etc/init.
sleep 2;
sudo /etc/init.
sleep 2;
done
...And guess, I got it, because in other term ran the following script:
~$ while true; do sudo hwclock --show; sleep 2; done
Password:
Fri 01 Sep 2006 12:39:07 AM CST -0.475796 seconds
select() to /dev/rtc to wait for clock tick timed out
select() to /dev/rtc to wait for clock tick timed out
Well, had to kill a lot of instances of hwclock that were running. I didn't know that script lauch a new instance each time.
My conclusion is, Ubuntu 6.06.1 with Linunx 2.6.17 is affected too, even using --directisa.
Anybody has a solution for this.
Regards,