From: Jeff Mahoney <jeffm@suse.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: jerome lacoste <jerome.lacoste@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Marie-Helene Lacoste <manies@tele2.fr>
Subject: Re: 2.6.12.3 clock drifting twice too fast (amd64)
Date: Tue, 16 Aug 2005 19:17:07 -0400 [thread overview]
Message-ID: <430273F3.2000204@suse.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0508161103360.7101@schroedinger.engr.sgi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christoph Lameter wrote:
> 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.
I am seeing similar results on my Acer Ferrari 4000 (Turion64 ML-37). It
does appear that time is running 2x normal time.
Booting with noapictimer cleared up the timing issues, though it did
introduce some IRQ badness.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFDAnPzLPWxlyuTD7IRAuQ+AKCoK4Bvj9YaSxK1cYzK/LQUGcj2pQCgmBKK
hGeSfGE+CvdNzqW3pN5LQq8=
=wtra
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-08-16 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 10:10 2.6.12.3 clock drifting twice too fast (amd64) jerome lacoste
2005-08-16 18:05 ` Christoph Lameter
2005-08-16 21:15 ` jerome lacoste
2005-08-16 23:17 ` Jeff Mahoney [this message]
2005-08-17 6:48 ` yhlu
2005-08-17 13:20 ` Jeff Mahoney
2005-08-17 15:11 ` yhlu
2005-08-16 21:41 ` john stultz
2005-08-16 23:11 ` jerome lacoste
2006-02-06 17:02 ` jerome lacoste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430273F3.2000204@suse.com \
--to=jeffm@suse.com \
--cc=clameter@engr.sgi.com \
--cc=jerome.lacoste@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manies@tele2.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox