On Wed, Aug 21, 2002 at 07:53:33PM -0400, Theo Van Dinter wrote:
it got funky, but I know what you're saying. I'll test externally after dinner.
Ok, so I got caught up after dinner ... ;) I did go and change the BIOS settings again, around 11pm on Wednesday. The problem then stayed away until ~4:12am on the 23rd.
I suggest writing down the value, counting five minutes with an EXTERNAL clock, such as a stopwatch, and then writing down the value again. (value2 - value1) / (60*5) should equal about 100.
Ok, here we go: (date as reported from different system) Fri Aug 23 09:50:26 EDT 2002 CPU0 0: 13720765 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 753652 XT-PIC serial 8: 1 XT-PIC rtc 10: 320822 XT-PIC eth0, eth1 11: 996123 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13720778 ERR: 4588 MIS: 0 Fri Aug 23 10:28:45 EDT 2002 CPU0 0: 13950661 XT-PIC timer 1: 3475 XT-PIC keyboard 2: 0 XT-PIC cascade 4: 761173 XT-PIC serial 8: 1 XT-PIC rtc 10: 326570 XT-PIC eth0, eth1 11: 1008701 XT-PIC 3ware Storage Controller 15: 190389 XT-PIC ncr53c8xx NMI: 0 LOC: 13950673 ERR: 4622 MIS: 0 The first thing I notice is that int 4 is getting hit quite a bit, and I have no idea why. The device hooked up to that serial port is a UPS, and shouldn't be generating so many interrupts. Hmmm. Anyway, between the two times is 38:19, or 2299 seconds. So: (13950661-13720765) / 2299 = 99.9982601130927 So that part seems ok. :| -- Randomly Generated Tagline: That is a known bug in 5.00550. Either an upgrade or a downgrade will fix it. -- Larry Wall in <6vu1vo$89c@kiev.wall.org>