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 09:20:39 GMT	[thread overview]
Message-ID: <201103100920.p2A9Kd3m028949@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12114-12968@https.bugzilla.kernel.org/>

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





--- Comment #16 from Thomas Renninger <trenn@suse.de>  2011-03-10 09:20:39 ---
> I can find oops like these in early dmesg
Yep, something is borked if one tries to disable tsc. Same with notsc boot
param.
No time to look at it right now, though.

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?

Can you double check that you did not use processor.max_cstate=1 and an
unmodified kernel. If there still is only C1 in /proc/acpi/processor/*/power
then it is something else.
Ok, local_apic_timer_c2_ok is set to 0 already by default and needs to get
enabled via boot param, this cannot be it.
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!.

-- 
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  9:20 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 [this message]
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

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=201103100920.p2A9Kd3m028949@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.