Hi, I'm getting the message in the subject when I run systat -vm on a lightly loaded server. Top shows interesting CPU usage %: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Some Googling tells me that a fix for this went in around 1998 in sys/i386/isa/clock.c, see http://www.geocrawler.com/archives/3/159/1998/7/0/777198/ (fix verified to be present in RELENG_4_8 which is what the machine is running). Since I'm the only one with this problem I'm assuming some hardware clock has died, but now I'm trying to find out which one exactly. Could this have to do with the battery-backed CMOS clock? If so how can I know for sure that that isn't working right? More information available on request. --Stijn -- "A mouse is a device used to point at the xterm you want to type in." -- Kim Alm, alt.sysadmin.recovery -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030627/d59b7a5a/attachment.bin
On Fri, 27 Jun 2003, Stijn Hoop wrote:> I'm getting the message in the subject when I run systat -vm on a > lightly loaded server. Top shows interesting CPU usage %: > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% > idle > > Some Googling tells me that a fix for this went in around 1998 in > sys/i386/isa/clock.c, see > > http://www.geocrawler.com/archives/3/159/1998/7/0/777198/ > > (fix verified to be present in RELENG_4_8 which is what the machine is > running). > > Since I'm the only one with this problem I'm assuming some hardware > clock has died, but now I'm trying to find out which one exactly. Could > this have to do with the battery-backed CMOS clock? If so how can I know > for sure that that isn't working right? > > More information available on request.Many vendors have hardware diagnostic CD's available on their web sites that test various aspects of the system, such as the accuracy of the clock, the proper functioning of timers, etc. You might want to give one a spin. Also, if you have any identical (or very similar hardware) that does or does not exhibit the problem, that would be interesting also. Speaking of systat -vmstat, in the interrupts column, what is the interrupt count for the rtc and clk lines? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Fri, Jun 27, 2003 at 13:52:08, stijn (Stijn Hoop) wrote about "alternate system clock has died": SH> I'm getting the message in the subject when I run systat -vm on a lightly SH> loaded server. Top shows interesting CPU usage %: SH> CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle See LINT: # Notes on APM # The flags takes the following meaning for apm0: # 0x0020 Statclock is broken. # If apm is omitted, some systems require sysctl -w kern.timecounter.method=1 # for correct timekeeping. This is possibly the first thing should be done seeing dead statclock. It was actual for SMP motherboards based on 440BX and similar chipsets.> Could this have to do > with the battery-backed CMOS clock?Yes, statclock is RTC interrupts, but even if battery is dead, interrupts should work. -netch-