During startup hwclock.sh is run more then once. In rare cases they overlap causing the PC RTC to become non-functional. This is because the second copy of hwclock falls back to using IOPL and direct I/O instructions after it fails to open /dev/rtc (already owned by the first copy of hwclock). The RTC hardware is not designed for such uncontrolled access.
During startup hwclock.sh is run more then once. In rare cases they overlap causing the PC RTC to become non-functional. This is because the second copy of hwclock falls back to using IOPL and direct I/O instructions after it fails to open /dev/rtc (already owned by the first copy of hwclock). The RTC hardware is not designed for such uncontrolled access.