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: Sat, 15 Sep 2012 12:34:29 +0200 [thread overview]
Message-ID: <20120915103429.GA12364@liondog.tnic> (raw)
In-Reply-To: <CAPL5yKdyDk8RdDhYWHHjQXVb1G6+9xqDKQgGrTZ4UZ1+6fOvRA@mail.gmail.com>
On Fri, Sep 14, 2012 at 09:34:52PM -0400, Dan Merillat wrote:
> I didn't want to re-flash it,
That's perfectly understandable :)
> but I went ahead and cleared the CMOS, then went in and re-enabled the
> power-management functions (back to "Auto")
>
> [ 0.000000] Linux version 3.6.0-rc4-dan-00128-geeea3ac (harik@fileserver) (g
> cc version 4.7.1 (Debian 4.7.1-2) ) #2 SMP PREEMPT Fri Sep 7 06:30:20 EDT 2012
> ...
> [ 0.000000] ACPI: SSDT 00000000c7de9640 00248 (v01 PTLTD POWERNOW
> 00000001 LTP 00000001)
> ...
> [ 22.601027] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core
> Processor 4600+ (2 cpu cores) (version 2.20.00)
> [ 22.601328] powernow-k8: fid 0x10 (2400 MHz), vid 0xc
> [ 22.601366] powernow-k8: fid 0xe (2200 MHz), vid 0xe
> [ 22.601402] powernow-k8: fid 0xc (2000 MHz), vid 0x10
> [ 22.601438] powernow-k8: fid 0xa (1800 MHz), vid 0x10
> [ 22.601476] powernow-k8: fid 0x2 (1000 MHz), vid 0x12
>
> So damned if I know why the BIOS quit exporting the SSDT, I'll chalk
> it up to bit-rot. As far as I can tell, every BIOS setting is the
> same as before I wiped it.
Ha!
Clearing the CMOS helped in Adko's case with the random reboots too. I
have to make a mental note to myself to tell people to first clear their
CMOS when they're reporting strange issues related to BIOS.
Btw, I'll chalk this to whatever the monkeys have been smoking at the
time they've been writing your BIOS. Boy, if I could get a cent for
every BIOS bug out there...
Great, one more bug fixed. Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-15 10:34 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
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 [this message]
-- 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=20120915103429.GA12364@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