Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Borislav Petkov <bp@alien8.de>
Cc: Adko Branil <adkobranil@yahoo.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: HDD problem, software bug, bios bug, or hardware ?
Date: Mon, 27 Aug 2012 09:50:55 +0200	[thread overview]
Message-ID: <201208270950.55590.rjw@sisk.pl> (raw)
In-Reply-To: <20120825113301.GA15210@liondog.tnic>

On Saturday, August 25, 2012, Borislav Petkov wrote:
> On Fri, Aug 24, 2012 at 06:31:11PM -0700, Adko Branil wrote:
> > To add some more info - i just noticed in dmesg of the latest kernel-2.5.2 some suspicious lines:
> > 
> > 	* [   44.251706] microcode: AMD CPU family 0xf not supported
> > 	* [   44.255721] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2 cpu cores) (version 2.20.00)
> > 	* [   44.255736] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found.
> > 	* [   44.255736] [Firmware Bug]: powernow-k8: Try again with latest BIOS.
> > 
> > Coult it be related to the crashes , and should i update my bios ?
> 
> No.
> 
> Try to enable the Cool'n'Quiet option in your BIOS - this message should
> disappear then.
> 
> Btw, there's a patch to make this more understandable:
> 
> http://marc.info/?l=linux-kernel&m=134262430326493
> 
> Rafael, this one is queued for 3.7, I assume?

Well, it should be, but I seem to have failed to merge my pm-cpufreq-next branch
into linux-next.  Sorry about that, will fix when I get back home from the
KS/LinuxCon.

Thanks,
Rafael

  reply	other threads:[~2012-08-27  7:44 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 [this message]
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
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=201208270950.55590.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=adkobranil@yahoo.com \
    --cc=bp@alien8.de \
    --cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox