David Malone wrote: >On Sun, Jan 11, 2004 at 11:50:35AM -0500, Scott W wrote: > > >>Not sure this helps in any immediate fashion, but another data point.... >> >> > >I think this problem is usually caused by one of the clock interrupts >stopping. Checking the output of "vmstat -i" can confirm this - check >for: > >clk irq0 1044322763 100 >rtc irq8 1352668148 129 > >The rate for the first one should 100 (Or possibly HZ, if you have >adjusted HZ). The rate of the second should be about 128, unless >things have got confused. > > David. > > > Things are in fact working correctly on my system at the moment, although I'll certainly check this if I experience the same issue again. Current output of vmstat -i: [wegster_at_freeb] /home/wegster [1] $ vmstat -i interrupt total rate irq1: atkbd0 10 0 irq3: sio1 2 0 irq4: sio0 2 0 irq6: fdc0 4 0 irq8: rtc 20265654 127 irq9: ohci0 1 0 irq12: psm0 279 0 irq13: npx0 1 0 stray irq13 1 0 irq14: ata0 30 0 irq20: ips0 62763 0 irq27: pcn0 3186839 20 irq0: clk 15829921 99 Total 39345507 248 ScottReceived on Sun Jan 11 2004 - 09:10:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:37 UTC