public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jason Vas Dias <jvdias@research.att.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	andi@firstfloor.org, roland@redhat.com, molnar@redhat.com,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.27 kernel disables frequency switching on x86_64 - stuck on lowest frequency
Date: Fri, 26 Sep 2008 08:17:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0809260806120.3265@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200809260201.42206.jvdias@research.att.com>



On Fri, 26 Sep 2008, Jason Vas Dias wrote:
> 
> There appears to be a serious problem with every 2.6.27-X kernel I've 
> tried - and I've tried quite a few from the linux-2.6, linux-acpi-2.6, 
> and linux-2.6-tip GIT trees, and the latest Fedora 10 kernels over the 
> past few weeks trying to solve this problem:

So which trees work, and which don't? Also, since it seems entirely 
repeatable, this is a prime candidate for "git bisect" - it will be 
eventually faster to do than trying many different trees at random, even 
if you will likely need to reboot/compile about 12 times or so (assuming 
2.6.27-rc1 is broken, and 2.6.26 works, which it sounds like).

Bisecting really isn't that hard. Get the git tree, do

	git bisect start
	git bisect bad v2.6.27-rc1
	git bisect good v2.6.26

and off you go. You don't even need to know a lot about git, there's a few 
quick tutorials out there if you haven't used it. See for example

	http://www.kernel.org/doc/local/git-quick.html

which has an example git bisect run, in addition to just initial clone 
insutrctions.

> CPU frequency switching is completely disabled, the 2.2Ghz AMD TL-64 
> Dual Core CPU is stuck at 0.8Ghz, the machine cannot reboot or perform 
> any ACPI actions.
> 
> There are no obvious failures indicated in the logs, only this:
> 
> [    0.000000] ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock": [00008800] [0000000000008100], using 64X [20080609]

Hmm. I don't know if it's ACPI-related, but the fact that it cannot even 
reboot etc sure seems to make it likely. Have you made the acpi lists 
aware of it (linux-acpi@vger.kernel.org and lenb are listed in 
MAINTAINERS)?

		Linus

       reply	other threads:[~2008-09-26 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200809260201.42206.jvdias@research.att.com>
2008-09-26 15:17 ` Linus Torvalds [this message]
2008-09-26 15:40   ` 2.6.27 kernel disables frequency switching on x86_64 - stuck on lowest frequency Zhao Yakui

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=alpine.LFD.1.10.0809260806120.3265@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=jvdias@research.att.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=molnar@redhat.com \
    --cc=roland@redhat.com \
    /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