Date: Mon, 30 Jun 2003 23:50:57 +0300 From: Valentin Nechayev <netch@iv.nn.kiev.ua> To: Stijn Hoop <stijn@win.tue.nl> Cc: stable@freebsd.org Subject: Re: alternate system clock has died Message-ID: <20030630205057.GA2249@iv.nn.kiev.ua> In-Reply-To: <20030627115208.GC90536@pcwin002.win.tue.nl> References: <20030627115208.GC90536@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030630205057.GA2249>