public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier Fourdan <fourdan@xfce.org>
To: linux-kernel@vger.kernel.org
Subject: Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting]
Date: Tue, 29 Mar 2005 23:28:34 +0200	[thread overview]
Message-ID: <1112131714.14248.8.camel@shuttle> (raw)
In-Reply-To: <20050328193921.GW30052@alpha.home.local>

Hi all

Following my own thread, I found the following error in dmesg:

    PM-Timer running at invalid rate: 33% of normal - aborting.

I found that interesting because 33% is 1/3 and the clock runs exactly
3x faster than normal...

A bit of search on google gave me several links to posts from other
people with the exact same problem on similar hardware (AMD64 laptop)
but I couldn't find neither the cause nor the fix of that issue (as I
think it might be related to the other issues I observe when the clock
goes too fast)

Does that PM-Timer message makes sense to someone knowledgeable?

Thanks in advance,

Cheers,
Olivier.

On Mon, 2005-03-28 at 21:39 +0200, Willy Tarreau wrote:
> On Mon, Mar 28, 2005 at 09:30:26PM +0200, Olivier Fourdan wrote:
> > Hi Willy
> > 
> > On Mon, 2005-03-28 at 21:20 +0200, Willy Tarreau wrote:
> > > Now I have a compaq (nc8000) which does not exhibit such buggy behaviour,
> > > but you can try disabling the APIC too just in case it's a similar problem
> > > (at least in 32 bits, I don't know if you can disable it in 64 bits mode).
> > 
> > Thanks for the hint, but unfortunately, it's one of the first things I
> > tried, and that makes no difference.
> 
> Sorry, at first I only noticed ACPI in your mail, but after reading it
> again, I also noticed APIC. So now, you can only try not to initialize
> some peripherals (IDE, network, display, etc...) by removing their drivers
> from the kernel. You may end up with a kernel panic, but that does not
> matter is you boot it with "panic=5" so that it automatically reboots
> 5 seconds after the panic. You should then finally identify the subsystem
> which is responsible for your problems. Perhaps you'll even need to remove
> PCI support :-(
> 
> Regards,
> Willy
> 
> 



  parent reply	other threads:[~2005-03-29 21:29 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       ` Olivier Fourdan [this message]
2005-03-29 22:02         ` Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting] Olivier Fourdan
2005-03-29 22:11           ` Dominik Brodowski
2005-03-29 22:11           ` john stultz
2005-03-31 19:12             ` Olivier Fourdan

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=1112131714.14248.8.camel@shuttle \
    --to=fourdan@xfce.org \
    --cc=linux-kernel@vger.kernel.org \
    /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