From: Zhao Yakui <yakui.zhao@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: "Langsdorf, Mark" <mark.langsdorf@amd.com>,
lkml <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Regression in 2.6.27-rc2 in acpi_processor_init()
Date: Sun, 10 Aug 2008 11:34:36 +0800 [thread overview]
Message-ID: <1218339276.6671.43.camel@yakui_zhao.sh.intel.com> (raw)
In-Reply-To: <200808082302.11358.rjw@sisk.pl>
On Fri, 2008-08-08 at 23:02 +0200, Rafael J. Wysocki wrote:
> [Adding CCs]
>
Hi, Mark
Will you please attach the output of acpidump on bug 11287?
Of course it will be great if you can enable CONFIG_ACPI_DEBUG and
CONFIG_CPUFREQ_DEBUG in kernel configuration and boot the system with
the option of "cpufreq.debug=7 acpi.debug_layer=0x01010000
acpi.debug_level=0x17".
After the system is booted, please attach the output of dmesg.
Please do the above test on both kernel 2.6.27-rc1 and 2.6.27-rc2.
Thanks.
> On Friday, 8 of August 2008, Langsdorf, Mark wrote:
> > I got a regression when updated from 2.6.27-rc1 ro
> > 2.6.27-rc2. The noticeable symptom is the powernow-k8
> > driver stopped working because the call to
> > acpi_processor_register_performance() is returning
> > -EINVAL.
> >
> > Digging into the code a bit more, that's occurring
> > because acpi_processor_ppc_status is not set.
> > That should be set in acpi_processor_init(), but
> > that function is failing to register the ACPI
> > processor driver.
> >
> > I've dug through the code and can't see why
> > that call would fail. It doesn't look like there
> > were any changes between 2.6.27-rc1 and 2.6.27-rc2,
> > but I may have missed something.
> >
> > Any advice or suggestions in debugging this
> > appreciated.
> >
> > -Mark Langsdorf
> > Operating System Research Center
> > AMD
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-10 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 19:36 Langsdorf, Mark
2008-08-08 21:02 ` Rafael J. Wysocki
2008-08-08 21:06 ` Dave Jones
2008-08-10 3:34 ` Zhao Yakui [this message]
2008-08-11 16:54 ` Langsdorf, Mark
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=1218339276.6671.43.camel@yakui_zhao.sh.intel.com \
--to=yakui.zhao@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®