[2.4.16] Clock locking bugs?

From: Simon Kirby (sim@netnation.com)
Date: Mon Jan 14 2002 - 13:02:15 EST


Just had a server's clock stop at 9:02:30am. Very interesting
results:

[sroot@pro:/]# cat /proc/interrupts
           CPU0 CPU1
  0: 172839353 172896882 IO-APIC-edge timer
  1: 578 522 IO-APIC-edge keyboard
  2: 0 0 XT-PIC cascade
  4: 22002 21840 IO-APIC-edge serial
 10: 581309135 580556518 IO-APIC-level eth0
 12: 63077142 63023533 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 345979794 345980089
ERR: 0
MIS: 0

...

[sroot@pro:/]# cat /proc/interrupts
           CPU0 CPU1
  0: 172839353 172896882 IO-APIC-edge timer
  1: 578 522 IO-APIC-edge keyboard
  2: 0 0 XT-PIC cascade
  4: 22002 21840 IO-APIC-edge serial
 10: 581309219 580556518 IO-APIC-level eth0
 12: 63077142 63023533 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 345979883 345980178
ERR: 0
MIS: 0

Alan says this is due to locking problems with the timer I/O code.

On the console were a lot of "set_rtc_mmss: can't update from 79 to 32"
type messages that have always happened on SMP kernels with ntpd.

Has anybody created any patches for this?

Simon-

[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:46 EST