From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 12114] AthlonXP-M
Date: Thu, 10 Mar 2011 11:35:36 GMT [thread overview]
Message-ID: <201103101135.p2ABZa01029892@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12114-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=12114
--- Comment #18 from Dominique Larchey-Wendling <larchey@loria.fr> 2011-03-10 11:35:35 ---
(In reply to comment #16)
> That your system only shows C1 is strange.
> The message you showed:
> > Marking TSC unstable due to TSC halts in idle
> should only show up if C2 or deeper states (or C1E, but this should not exist
> on older machines?) are supported.
> Compare with drivers/acpi/processor_idle.c:
> if (state > ACPI_STATE_C1)
> mark_tsc_unstable("TSC halts in idle");
> Could it be that you tried with processor.max_cstate=1?
Yes yes I did use this command line parameter. So the fact that my system only
shows C1 is normal in this case I suppose. I will try to boot the system
without the processor.max_cstate=1 parameter.
> Also a wiki page about this processor tells that the new "mobile" (only
> AthlonXP "M") feature is to support Powernow!. So it really might have to do
> with tsc+powernow!.
Powernow does not work on my system.
----------------------------------------------------------------------------
[ 121.157837] Fast TSC calibration using PIT
[ 121.170872] powernow: Trying ACPI perflib
[ 121.170930] powernow: ACPI perflib can not be used on this platform
[ 121.170973] powernow: ACPI and legacy methods failed
-----------------------------------------------------------------------------
I bought the XP-M on Ebay. My mainboard (a FX41 from Shuttle) was not supposed
to run mobile Athlon so I think the BIOS does not support the XP-M. I will try
patches from
http://www.yggdrasl.demon.co.uk/code/
but I need to guess the correct parameters to manually configure Powernow on my
Athlon.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-03-10 11:35 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 [this message]
2011-03-10 12:47 ` bugzilla-daemon
2011-03-10 13:21 ` bugzilla-daemon
2011-03-10 16:22 ` bugzilla-daemon
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=201103101135.p2ABZa01029892@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.