Hello,

well that lately has happend to me on very new hardware from IBM while running:

• hwlclock --systohc

I am quite unsure about the cause, but in the init.d scripts I have found this addition which works:

• hwclock --systohc --directisa