On Tuesday 19 May 2009, Mick wrote: > A couple of days ago chronyd stopped functioning. > > This is all that the logs tell me but I don't know what I can do to fix it: > ================================================================= > May 19 06:25:13 lappy chronyd[6756]: chronyd version 1.23 starting > May 19 06:25:14 lappy chronyd[6756]: Set system time, error in RTC > = -306.664140 > May 19 06:25:14 lappy chronyd[6756]: Set system time, error in RTC > = -306.664140 > May 19 06:30:20 lappy chronyd[6756]: Initial txc.tick=10000 txc.freq=0 > (0.00000000) txc.offset=0 => hz=100 shift_hz=7 > May 19 06:30:20 lappy chronyd[6756]: Initial txc.tick=10000 txc.freq=0 > (0.00000000) txc.offset=0 => hz=100 shift_hz=7 > May 19 06:30:20 lappy chronyd[6756]: set_config_hz=0 hz=100 shift_hz=7 > basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 > max_tick_bias=1000 > May 19 06:30:20 lappy chronyd[6756]: set_config_hz=0 hz=100 shift_hz=7 > basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 > max_tick_bias=1000 > May 19 06:30:20 lappy chronyd[6756]: Linux kernel major=2 minor=6 patch=28 > May 19 06:30:20 lappy chronyd[6756]: Linux kernel major=2 minor=6 patch=28 > May 19 06:30:20 lappy chronyd[6756]: calculated_freq_scale=0.99902439 > freq_scale=0.99902439 > May 19 06:30:20 lappy chronyd[6756]: calculated_freq_scale=0.99902439 > freq_scale=0.99902439 > May 19 06:30:20 lappy chronyd[6756]: Could not start measurement : > Inappropriate ioctl for device > May 19 06:30:20 lappy chronyd[6756]: Could not read flags /dev/rtc : > Input/output error > May 19 06:30:20 lappy chronyd[6756]: Could not stop measurement : > Inappropriate ioctl for device > ================================================================= > > # ls -al /dev/rtc > crw-r--r-- 1 root root 10, 135 May 19 06:24 /dev/rtc > > When I try to check /dev/rtc I get: > > # cat /dev/rtc > cat: /dev/rtc: Input/output error > > I should be getting resource busy instead. > > I suspect that this problem started when I changed my kernel to 2.6.28-r5. > I noticed it comes up with a APIC error on booting, could this be related?
Yep, it was related to the kernel, or to be more precise it was related to HPET being enabled in the kernel. For some reason it clashed ... How can I tell if my CPU/MoBo supports HPET? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
