DragonFly BSD
DragonFly bugs List (threaded) for 2004-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Problems with clock on 1.1-CURRENT

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 4 Aug 2004 10:34:58 -0700 (PDT)

:$ kldstat
:Id Refs Address    Size     Name
: 1    1 0xc0100000 2e0244   kernel
:$ sysctl -a | grep acpi
:$ sysctl -a | grep apm
:I noticed when I used this system, sometimes my system clock stopped.
:For a minutes if there is no input from the keyboard or the mouse it has
:happened. The clock restart when input comes, but the starting time is
:same time when it stops.
:What can I try?  Please tell me.
:H.Miyamoto (aka "Yuukis"). <Ys@xxxxxxxxxxxxxx>

    That kinda sounds like the clock interrupt isn't running at all, or
    its IRQ is being routed from another source, or something equally bad.

    Do a 'systat -vm 1' in a window and observe the 'clk' interrupts on
    irq0 in various situations.  A normally working, idle system should
    get a fairly constant 245-250 clk interrupts per second.  [Of course,
    systat's 1 second interval might also be messed up due to the issue].

    Your 'dmesg' output would be useful.

					Matthew Dillon 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]