From: Olivier Fourdan <fourdan@xfce.org>
To: john stultz <johnstul@us.ibm.com>,
Dominik Brodowski <linux@dominikbrodowski.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting]
Date: Thu, 31 Mar 2005 21:12:37 +0200 [thread overview]
Message-ID: <1112296357.6027.20.camel@shuttle> (raw)
In-Reply-To: <1112134312.17854.55.camel@cog.beaverton.ibm.com>
Hi John, Dominik,
On Tue, 2005-03-29 at 14:11 -0800, john stultz wrote:
> Yea. From your description this is most likely the cause of the issue.
> Currently the time of day is still tick-based, using the tsc/pmtmr/hpet
> only for interpolating between ticks.
Sorry for the late follow up. Unfortunately, a quick hack to disable the
"pmtmr" check shows that even when "trusting" the PM-Timer, the clock
and interrupts still run 3x too fast. That makes no difference.
> Well, if you tried the time of day re-work I've been working on it would
> mask the issue somewhat, but you'd still have the problem that you are
> taking too many timer interrupts.
Where could I get that patch from ? I'd be glad to do some testing for
you if you need it.
> One thing you could try is playing with the CLOCK_TICK_RATE value to see
> if you just have very unique hardware.
Problem is that the issue shows exactly after one quick power off/power
on sequence. It doesn't show after a real cold start (leaving the laptop
off for a couple of hours) or even after a reboot.
> A similar sounding issue has also been reported here:
> http://bugme.osdl.org/show_bug.cgi?id=3927
Not sure if that's the exact same problem. What I can say, after reading
that bug report, is that disabling ACPI and/or APIC makes no difference.
Specifying the clock=... makes no difference either. It doesn't seem
related to the AMD64 part of the kernel since it shows equally when
using a 64bit kernel and a 32bit kernel.
Moreover, when that bug shows, there are other different problems
showing (such as the cdrom not being to mount anything, or ndiswrapper
crashing the system with a MCE error).
At first, I thought the issue might be related to the nforce3, but the
bug refers to an ATI chipset so I guess it's not related to the nforce.
Anyway, it doesn't seem to be an uncommon issue with AMD64 based
hardware. I don't know where to start from though.
Cheers,
Olivier.
prev parent reply other threads:[~2005-03-31 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:56 Various issues after rebooting Olivier Fourdan
2005-03-28 19:20 ` Willy Tarreau
2005-03-28 19:30 ` Olivier Fourdan
2005-03-28 19:39 ` Willy Tarreau
2005-03-28 20:10 ` Olivier Fourdan
2005-03-29 21:28 ` Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting] Olivier Fourdan
2005-03-29 22:02 ` Olivier Fourdan
2005-03-29 22:11 ` Dominik Brodowski
2005-03-29 22:11 ` john stultz
2005-03-31 19:12 ` Olivier Fourdan [this message]
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=1112296357.6027.20.camel@shuttle \
--to=fourdan@xfce.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.