Re: 2.6.12.3 clock drifting twice too fast (amd64)

From: Christoph Lameter (clameter_at_engr.sgi.com)
Date: 08/16/05

  • Next message: Steven Rostedt: "Re: 2.6.13-rc6-rt6" 
    Date:	Tue, 16 Aug 2005 11:05:20 -0700 (PDT)
To: jerome lacoste <jerome.lacoste@gmail.com>

    On Tue, 16 Aug 2005, jerome lacoste wrote:

    > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme
    > AX 300 SE/t mainboard.
    >
    > I remember seeing a message in the boot saying something along:
    >
    > "cannot connect to hardware clock."
    >
    > And now I see that the time is changing too fast (about 2 seconds each second).

    The timer interrupt is probably called twice for some reason and therefore
    time runs twice as fast. Try using HPET for interrupt timing.

    > I don't have visual on the boot sequence anymore (only remote access).

    Use serial console or netconsole. The boot information is logged. Try
    dmesg.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Steven Rostedt: "Re: 2.6.13-rc6-rt6"

    Relevant Pages

    • Re: 2.6.12.3 clock drifting twice too fast (amd64)
      ... > The timer interrupt is probably called twice for some reason and therefore ... > time runs twice as fast. ... >>I don't have visual on the boot sequence anymore. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.12.3 clock drifting twice too fast (amd64)
      ... > AX 300 SE/t mainboard. ... > I remember seeing a message in the boot saying something along: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)