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 13:21:01 GMT	[thread overview]
Message-ID: <201103101321.p2ADL1Sp026937@demeter2.kernel.org> (raw)
In-Reply-To: <bug-12114-12968@https.bugzilla.kernel.org/>

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





--- Comment #20 from Thomas Renninger <trenn@suse.de>  2011-03-10 13:21:01 ---
I expect C2 is causing the trouble. processor.max_cstate=1 is the workaround
that should help.
Patch/test from comment #17 won't help.
As this machine is a bit older it might not even have an hpet timer?
(dmesg |grep -i hpet). If apic (and pic?) and tsc do not work due to the sleep
state and the machine does not have an hpet, there aren't much timers left for
time keeping?
But I won't be able to help you further there, you'd need to debug which timer
still ticks in C2 (and whether there still is one functioning at all) and
whether timer interrupts are still fired at the right times.
nohz=off is an option you might want to try with C2 enabled.

-- 
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 13:21 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 [this message]
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=201103101321.p2ADL1Sp026937@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.