linux-kernel - Re: Intel DP55KG BIOS Bug (reboot hangs, is Intel aware of the problem?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Oct 2009 17:01:49 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	"H. Peter Anvin" <hpa@...or.com>, Bryan Donlan <bdonlan@...il.com>
cc:	linux-kernel@...r.kernel.org, bruce.w.allan@...el.com
Subject: Re: Intel DP55KG BIOS Bug (reboot hangs, is Intel aware of the
 problem?)

On Thu, 15 Oct 2009, H. Peter Anvin wrote:

> On 10/14/2009 03:02 PM, Justin Piszcz wrote:
>> Hi,
>>
>> I have tried the following kernel parameters with '*' and reboot=b,
>> reboot=h and reboot=s.
>>
>
> reboot=t (triple), reboot=p (pci) and reboot=a (acpi) would be useful to
> test, too.
>
> 	-hpa
>

Thanks,

I find it kind of funny I tried the 4-5 options that didn't work first, 
bad luck?

Here is what worked and what did not and what I ended up using:

reboot=a * SUCCESS
reboot=b * FAIL
reboot=cold * FAIL
reboot=efi * FAIL
reboot=force * FAIL
reboot=h * FAIL
reboot=p * SUCCESS
reboot=s * FAIL
reboot=t * SUCCESS
reboot=warm * FAIL

I am using reboot=a for now, until INTEL releases a BIOS fix for this bug.

>From Bryan:

Try each of the following in the reboot= parameter: acpi, smp (32-bit
only), triple, efi, pci, warm, cold, force If one of them works, report 
it, along with the output from dmidecode and lspci -nn, so a workaround
entry can be added.

dmidecode & lspci below--

http://home.comcast.net/~jpiszcz/20091015/dmidecode.txt
http://home.comcast.net/~jpiszcz/20091015/lspci-nn.txt

Justin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/