[Bug 563618] Re: Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem

Steve Langasek steve.langasek at canonical.com
Fri Apr 23 21:54:49 UTC 2010


Have reviewed the change; should not impact boot performance or
reliability on systems not booting with 'fixrtc', installs to the
correct point in the boot sequence.  Still an ugly hack, but we already
knew that. :)  The only change I'm making is to drop the superfluous
call to hwclock --systohc -- we simply don't care about the value in the
hardware clock because we're not going to be reading from it at all
after this point, and writing this out delays the boot unnecessarily.
/etc/init/hwclock-save.conf will write it out for us on shutdown, for
all the good that does on the affected hardware.

Merged and uploading.

-- 
Ignoring a broken clock results in infinite reboots; not ignoring results in fsck failure; no solution to this problem
https://bugs.launchpad.net/bugs/563618
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.




More information about the kernel-bugs mailing list