public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier Fourdan <fourdan@gmail.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Assume PM Timer to be reliable on broken board/BIOS
Date: Wed, 10 Aug 2005 22:29:26 +0200	[thread overview]
Message-ID: <60f2b0dc05081013296a0a7938@mail.gmail.com> (raw)
In-Reply-To: <42E6C86F.3010503@shaw.ca>

On 7/27/05, Robert Hancock <hancockr@shaw.ca> wrote:
> > In a nutshell, sometimes, the PIT/TSC timer runs 3x too fast [1]. That
> > causes many issues, including DMA errors, MCE, and clock running way too
> > fast (making the laptop unusable for any software development). So far,
> > no BIOS update was able to fix the issue for me.
> 
> Shouldn't this be looked into further rather than adding this
> workaround? Surely Windows is using the PIT as well, so there must be
> some way to get it to behave properly..

Sorry for the late follow up. Well, the timer management in Windows
depends on the HAL used. By default, it's the ACPI HAL that is used in
this laptop.

I did re-install Windows by forcing the "Standard PC"  HAL in Windows
XP installation and, without ACPI, Windows exhibits the exact same
problem as Linux or any other system: The clock runs 3 times too fast
in Windows too...

So my guess is that the HAL ACPI in Windows does more or less the same
thing that does my patch (updated, available here:
http://www.xfce.org/~olivier/r3000), it calibrates the PIT timer based
on the ACPI (PM) timer.

Cheers,
Olivier.

  parent reply	other threads:[~2005-08-10 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4uGpt-2Y3-15@gated-at.bofh.it>
2005-07-26 23:34 ` PATCH: Assume PM Timer to be reliable on broken board/BIOS Robert Hancock
2005-07-27  5:32   ` Olivier Fourdan
2005-08-10 20:29   ` Olivier Fourdan [this message]
2005-07-26 22:32 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=60f2b0dc05081013296a0a7938@mail.gmail.com \
    --to=fourdan@gmail.com \
    --cc=hancockr@shaw.ca \
    --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