public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	"andreas.herrmann3" <andreas.herrmann3@amd.com>,
	Richard <tuxbox.guru@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>,
	eumaster@gmail.com, uli.geins@geins-web.de
Subject: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled
Date: Mon, 16 Jun 2008 19:47:53 +0200	[thread overview]
Message-ID: <1213638474.1684.21.camel@queen.suse.de> (raw)

Hi,

we got a bit further, Evgeny was able to get C-states working with
"nohz=off highres=off" boot parameters.

A short summary what has been found out that far:
  - apic timer breaks on C2 or deeper
  - noapictimer workaround helps to come a bit further, but results in sever
    other errors (see comment #13)
  - "nohz=off highres=off" works (tested on 2.6.25.4-8-pae and
    2.6.22.17-0.1-default SUSE kernels)
  - processor.max_cstate=1 works
  - This affects AMD Mobile Semprons (at least 3500+ and 3600+)


The output of /proc/acp/processor/*/power without highres/nohz
looks promising:
states:
    C1:                  type[C1] promotion[C2] demotion[--] latency[000]
usage[00000030] duration[00000000000000000000]
    C2:                  type[C2] promotion[C3] demotion[C1] latency[005]
usage[00002135] duration[00000000000011279621]
   *C3:                  type[C3] promotion[--] demotion[C2] latency[020]
usage[00034222] duration[00000000000228307174]


Also see bug:
https://bugzilla.novell.com/show_bug.cgi?id=396220
and some posts from Richard on the linux-acpi list.


This seem to be a mainline kernel regression since the nohz/highres
patches have been added.
I do not own such a machine myself (Richard, Evgeny, Uli (and Anvin?)
have such a machine and already helped to come that far).

Also the highres/nohz parts are a dark area to me... Any pointer how to
debug (or debug patches or patches to test), where to look at, etc. is
very much appreciated.

Thanks,

   Thomas


             reply	other threads:[~2008-06-16 17:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 17:47 Thomas Renninger [this message]
2008-06-16 17:54 ` AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled H. Peter Anvin
2008-06-16 20:06   ` Richard
2008-07-16 16:27 ` [PATCH] " Thomas Renninger
2008-07-16 19:03   ` Thomas Gleixner
2008-07-16 19:56     ` Thomas Renninger
2008-07-17  6:55       ` Richard
2008-07-17 10:51         ` Thomas Gleixner
2008-07-17 11:58           ` Richard
2008-07-17 11:11             ` Thomas Gleixner
2008-07-17 12:23               ` Richard
2008-07-17 12:03                 ` Thomas Gleixner
2008-07-17 17:47                   ` Richard
2008-07-17 16:59                     ` Thomas Gleixner
2008-07-18 11:03                       ` Richard
2008-07-18 17:12                       ` Richard
2008-07-18 17:14                       ` Richard
2008-07-18 17:15                       ` Richard
2008-07-17 10:32     ` Thomas Renninger
2008-07-17 11:44       ` Richard
2008-07-17 11:05         ` Thomas Gleixner

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=1213638474.1684.21.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=eumaster@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tuxbox.guru@gmail.com \
    --cc=uli.geins@geins-web.de \
    /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