From: Robert Hancock <hancockr@shaw.ca>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: ghpille@hotmail.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: system clock slow on Athlon AMD64 since 2.6.21
Date: Sun, 10 Jun 2007 12:02:00 -0600 [thread overview]
Message-ID: <466C3C98.8060800@shaw.ca> (raw)
In-Reply-To: <fa.o/++pztnlzntJf5yY17Qd7cKHWw@ifi.uio.no>
Mikael Pettersson wrote:
> On Fri, 08 Jun 2007 10:14:03 +0200, Gerard H. Pille wrote:
>> [1.] One line summary of the problem:
>> Since I switched from 2.6.20 to 2.6.21 on my Athlon AMD64 laptop, the system
>> time is slow - about 1' on 15'.
>
> According to your system description it seems that you have a
> Targa Visionary laptop with a VIA chipset and a Mobile Athlon64.
> If so, then you probably have the same problem I reported some time
> ago: see <http://marc.info/?l=linux-kernel&m=117681226421346&w=2>
> and the followup messages. The conclusion was that the chipset's
> ACPI PM timer slows down when the CPU is in C2.
>
> The workaround is to boot with processor.max_cstate=1.
Which, if true, is extremely bizarre, as the whole point and reason for
existence of the ACPI PM timer is that it NOT do this, and remain at the
same rate regardless of CPU power management changes..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-06-10 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.o/++pztnlzntJf5yY17Qd7cKHWw@ifi.uio.no>
2007-06-10 18:02 ` Robert Hancock [this message]
2007-06-11 10:51 ` PROBLEM: system clock slow on Athlon AMD64 since 2.6.21 Gerard H. Pille
2007-06-10 19:01 Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2007-06-09 14:53 Mikael Pettersson
2007-06-09 16:49 ` Disconnect
2007-06-09 19:27 ` Matthieu CASTET
2007-06-08 8:14 Gerard H. Pille
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=466C3C98.8060800@shaw.ca \
--to=hancockr@shaw.ca \
--cc=ghpille@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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