From: Andi Kleen <ak@muc.de>
To: Christopher Allen Wing <wingc@engin.umich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: clock runs at double speed on x86_64 system w/ATI RS200 chipset
Date: 5 Apr 2005 20:31:41 +0200
Date: Tue, 5 Apr 2005 20:31:41 +0200 [thread overview]
Message-ID: <20050405183141.GA27195@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0504051351200.13242@hammer.engin.umich.edu>
On Tue, Apr 05, 2005 at 02:02:20PM -0400, Christopher Allen Wing wrote:
>
> Are you thinking of blacklisting the APIC on this system until we figure
> out what's going on?
Some more debugging first might be good. Perhaps it is the same issue
many Nvidia boards have with the APIC timer override being wrong;
although in this case it should more not tick at all, but might
be still worth a try.
Try booting with acpi_skip_timer_override
-Andi
next prev parent reply other threads:[~2005-04-05 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 12:31 clock runs at double speed on x86_64 system w/ATI RS200 chipset Mikael Pettersson
2005-04-04 14:53 ` Christopher Allen Wing
2005-04-04 15:32 ` Mikael Pettersson
2005-04-04 21:42 ` Christopher Allen Wing
2005-04-05 17:18 ` Andi Kleen
2005-04-05 18:02 ` Christopher Allen Wing
2005-04-05 18:31 ` Andi Kleen [this message]
2005-04-05 18:49 ` Christopher Allen Wing
2005-04-05 19:10 ` Christopher Allen Wing
2005-04-05 19:46 ` Christopher Allen Wing
2005-04-06 20:36 ` Christopher Allen Wing
2005-04-06 22:13 ` [PATCH] Re: clock runs at double speed on x86_64 system w/ATI RS200 chipset (workaround for APIC mode?) Christopher Allen Wing
2005-04-07 7:37 ` Andi Kleen
2005-04-07 17:23 ` Christopher Allen Wing
2005-04-05 18:17 ` clock runs at double speed on x86_64 system w/ATI RS200 chipset (with APIC enabled) Christopher Allen Wing
-- strict thread matches above, loose matches on Subject: below --
2005-04-02 11:05 clock runs at double speed on x86_64 system w/ATI RS200 chipset Mikael Pettersson
2005-04-02 18:19 ` Christopher Allen Wing
2005-04-01 23:24 Christopher Allen Wing
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=20050405183141.GA27195@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wingc@engin.umich.edu \
/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