Re: alternate system clock has died

From: Robert Watson (rwatson_at_freebsd.org)
Date: 06/27/03

  • Next message: Robert Watson: "Re: apache panics on a recent 4.8-STABLE" 
    Date: Fri, 27 Jun 2003 09:39:06 -0400 (EDT)
To: Stijn Hoop <stijn@win.tue.nl>

    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

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Robert Watson: "Re: apache panics on a recent 4.8-STABLE"

    Relevant Pages

    • Re: Coding style, wait statement, sensitivity list and synthesis.
      ... >> least assume that XST supports this style and create this hardware. ... >>>then the higher precedence clock must be coded first. ... For these very rare dual-edge sensitive register, yes, I think instantiation ... Dual-edge sensitive register elements is not common practice in hardware design. ...
      (comp.lang.vhdl)
    • Re: [PATCH 06/23 -v8] handle accurate time keeping over long delays
      ... which is the same as the underlying hardware counter. ... So you are saying that you can trivally make it work with a clock that is, ... will never change while I am in the preempt disabled code. ... it's called from an IPI running on each CPU. ...
      (Linux-Kernel)
    • Re: Using different timebase for ntpd
      ... modified Ethernet devices to support hardware time stamping. ... was doing hardware gated ntp packets in the 90s. ... hardware timestamping is available from us. ... software timestamping using a hardware clock. ...
      (comp.protocols.time.ntp)
    • Re: beginner synthesize question - my debounce process wont synthesize.
      ... for the clock edge from the if for the enabling condition. ... but rather use it to describe hardware. ... mycount:= mycount + ... Now my process only does something on a RISING edge of the clock ...
      (comp.arch.fpga)
    • Re: Coding style, wait statement, sensitivity list and synthesis.
      ... Or they decided collectively not to implement the double-edge hardware feature to was that 1076.6 recommended it. ... there is a standard for coding styles? ... modeling the IBM style separate master-slave register hardware, which also allowed some pretty exotic scan/functional clock designs. ... In a design review, I require all multiple clock and clock ...
      (comp.lang.vhdl)