ok:

# vmstat -i
interrupt                   total       rate
ata0 irq14                     23          0
ahc0 irq10                     15          0
aac0 irq2                 6330470         30
fxp0 irq5                17556113         83
fdc0 irq6                       4          0
sio0 irq4                       8          0
sio1 irq3                       8          0
clk irq0                 21008332         99
rtc irq8                   264460          1
Total                    45159433        214

Now, when I repeat vmstat -i, all of these numbers (or rather, all of the
large numbers) increase _except_ for `rtc irq8`.

So is this just a simple broken clock on the system, as in, my hardware
clock is physically broken/breaking ?

dmesg says nothing about irq8, so I assume there is no conflict.

Further, regarding the APM conjecture, this is a server and (although I
may be mistaken) does not have APM in the bios at all - I have also
removed it from the kernel.  dmesg tends to confirm the absence of APM.

--bpat

On Mon, 26 Aug 2002, David Malone wrote:

> On Sun, Aug 25, 2002 at 04:49:23PM -0700, Patrick Thomas wrote:
> > Also, just to add a bit more info, sometimes instead of rebooting to solve
> > the problem, the problem doesn't exist, and rebooting causes it to
> > manifest.  So it seems fairly random.
>
> Can you watch "vmstat -i" before and after the problem occurs? I'm
> guessing that one of the interrupt counts will stop increasing.
>
>       David.
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to