From: Borislav Petkov <bp@alien8.de>
To: Dan Merillat <dan.merillat@gmail.com>
Cc: Adko Branil <adkobranil@yahoo.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: HDD problem, software bug, bios bug, or hardware ?
Date: Mon, 10 Sep 2012 22:51:22 +0200 [thread overview]
Message-ID: <20120910205121.GA11370@liondog.tnic> (raw)
In-Reply-To: <CAPL5yKcyzf1ta9Vc8Sh0EKCxBhonYjRFH7dnMEDBHbFYDh7u5w@mail.gmail.com>
On Sun, Sep 02, 2012 at 08:38:14PM -0400, Dan Merillat wrote:
> > Hmm, can you enable all the debug statements in the driver?
> >
> > Simply edit drivers/cpufreq/powernow-k8.c by adding
> >
> > #define DEBUG
>
> It didn't add anything new, got:
But it did, actually. The "trying to register..." is a pr_debug call for
example.
> [ 44.491795] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (2 cpu cores) (version 2.20.00)
> [ 44.491852] trying to register driver powernow-k8
this is cpufreq_register_driver()
> [ 44.491893] adding CPU 0
> [ 44.491955] processor_perflib-0423 [4294967293] processor_get_performa: ACPI-based processor performance control unavailable
this is acpi_processor_register_performance called by powernow_k8_cpu_init_acpi
> [ 44.492103] register performance failed: bad ACPI data: -5
> (I added the return value to the debug)
Yep, cool. This tells us that it is -EIO which means
that acpi_processor_register_performance returns -EIO
after trying acpi_processor_get_performance_info. The "..
performance control unavailable" message above tells us that
acpi_processor_get_performance_info fails when trying to get the _PCT
handle.
So, to recheck: are you sure your "Cool'n'quiet" option in the BIOS is
enabled? If not, please enable it and retest.
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-10 20:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 1:31 HDD problem, software bug, bios bug, or hardware ? Adko Branil
2012-08-25 11:33 ` Borislav Petkov
2012-08-27 7:50 ` Rafael J. Wysocki
2012-09-01 12:45 ` Dan Merillat
2012-09-02 7:24 ` Borislav Petkov
2012-09-03 0:38 ` Dan Merillat
2012-09-10 20:51 ` Borislav Petkov [this message]
2012-09-10 21:29 ` Dan Merillat
2012-09-10 21:59 ` Borislav Petkov
2012-09-15 1:34 ` Dan Merillat
2012-09-15 10:34 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2012-08-25 13:36 Adko Branil
2012-08-25 17:46 ` Adko Branil
2012-08-26 13:01 ` Borislav Petkov
2012-08-27 17:01 ` Adko Branil
2012-08-27 17:21 ` Felix Miata
2012-08-27 21:59 ` Borislav Petkov
2012-08-29 17:02 ` Adko Branil
2012-08-29 17:31 ` Adko Branil
2012-08-30 10:12 ` Borislav Petkov
[not found] ` <1346259574.81504.YahooMailNeo@web124706.mail.ne1.yahoo.com>
2012-08-30 9:58 ` Borislav Petkov
2012-08-30 10:11 ` Borislav Petkov
2012-08-30 11:10 ` Adko Branil
2012-09-02 20:04 ` Mikael Pettersson
2012-09-03 21:46 ` Adko Branil
2012-09-07 11:32 ` Adko Branil
2012-09-08 16:30 ` Mikael Pettersson
2012-09-08 17:22 ` Adko Branil
2012-09-11 13:38 ` Adko Branil
2012-09-10 9:15 ` Borislav Petkov
2012-09-10 9:17 ` Borislav Petkov
2012-08-25 0:54 Adko Branil
2012-08-25 2:58 ` Felix Miata
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=20120910205121.GA11370@liondog.tnic \
--to=bp@alien8.de \
--cc=adkobranil@yahoo.com \
--cc=dan.merillat@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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