All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 12114] AthlonXP-M
Date: Thu, 10 Mar 2011 16:22:13 GMT	[thread overview]
Message-ID: <201103101622.p2AGMDHP021904@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12114-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=12114





--- Comment #21 from Dominique Larchey-Wendling <larchey@loria.fr>  2011-03-10 16:22:11 ---
You are right the machine is a bit old. There is no HPET. The
processor.max_cstate=1 is indeed a simple workaround. powernow_k7.ko seems to
work with manual configuration but 

modprobe powernow-k7 fsb=133 overwrite_table=1 multiplier=75,105,135
switch_latency=650

has the immediate consequence that TSC becomes unstable (no because of C2 but
because of multiplier/frequency chance).

Mar 10 12:43:21 minipc klogd: [61408.385984] powernow: PowerNOW! Technology
present. Can scale: frequency and voltage.
Mar 10 12:43:21 minipc klogd: [61408.386033] powernow: Overwriting PST table
with manual settings
Mar 10 12:43:21 minipc klogd: [61408.386055] VID: 0xb (1.450V)
Mar 10 12:43:21 minipc klogd: [61408.386068] VID: 0xb (1.450V)
Mar 10 12:43:21 minipc klogd: [61408.386081] VID: 0xb (1.450V)
Mar 10 12:43:22 minipc klogd: [61408.386133] powernow: Minimum speed 997 MHz.
Maximum speed 1795 MHz.
Mar 10 12:43:22 minipc klogd: [61408.386192] Marking TSC unstable due to
cpufreq changes
Mar 10 12:43:22 minipc klogd: [61408.388262] Switching to clocksource acpi_pm

Since my server is not overheated and a working timer seems mandatory, I will
stick to the workaround 

processor.max_cstate=1 

Thank you very much for your help.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

      parent reply	other threads:[~2011-03-10 16:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12114-12968@https.bugzilla.kernel.org/>
2011-01-18  8:07 ` [Bug 12114] AthlonXP-M bugzilla-daemon
2011-03-03  1:27 ` bugzilla-daemon
2011-03-07 12:58 ` bugzilla-daemon
2011-03-07 17:23 ` bugzilla-daemon
2011-03-07 22:02 ` bugzilla-daemon
2011-03-08 10:02 ` bugzilla-daemon
2011-03-08 11:26 ` bugzilla-daemon
2011-03-09 15:39 ` bugzilla-daemon
2011-03-09 17:09 ` bugzilla-daemon
2011-03-10  9:20 ` bugzilla-daemon
2011-03-10  9:26 ` bugzilla-daemon
2011-03-10 11:35 ` bugzilla-daemon
2011-03-10 12:47 ` bugzilla-daemon
2011-03-10 13:21 ` bugzilla-daemon
2011-03-10 16:22 ` bugzilla-daemon [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=201103101622.p2AGMDHP021904@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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 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.