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-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0910141756440.2653@p34.internal.lan>
Date:	Wed, 14 Oct 2009 18:02:59 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org
cc:	bruce.w.allan@...el.com
Subject: Intel DP55KG BIOS Bug (reboot hangs, is Intel aware of the
 problem?)

Hi,

I have tried the following kernel parameters with '*' and reboot=b,
reboot=h and reboot=s.

-----------------------------------------------------------------------

Rebooting

    reboot=b[ios] | t[riple] | k[bd] | a[cpi] | e[fi] [, [w]arm | [c]old]
*   bios    Use the CPU reboot vector for warm reset
    warm   Don't set the cold reboot flag
    cold   Set the cold reboot flag
    triple Force a triple fault (init)
*   kbd    Use the keyboard controller. cold reset (default)
    acpi   Use the ACPI RESET_REG in the FADT. If ACPI is not configured or the
           ACPI reset does not work, the reboot path attempts the reset using
           the keyboard controller.
*   efi    Use efi reset_system runtime service. If EFI is not configured or the
           EFI reset does not work, the reboot path attempts the reset using
           the keyboard controller.

    Using warm reset will be much faster especially on big memory
    systems because the BIOS will not go through the memory check.
    Disadvantage is that not all hardware will be completely reinitialized
    on reboot so there may be boot problems on some systems.

*   reboot=force

None of which work.

-----------------------------------------------------------------------

It appears earlier Intel boards also suffered the same problem:

Subject: Re: Machine restart doesn't work - Intel 965G, 2.6.19-rc2
http://lkml.indiana.edu/hypermail/linux/kernel/0610.2/2215.html

Are those at Intel aware of this problem?

I have tried many different options/settings, nothing seems to work.

All workaround are unsuccessful.

It appears the dmidecode is requested for these sorts of problems, that is 
available here:
http://home.comcast.net/~jpiszcz/20091014/dmidecode.txt

Are there any other workarounds until Intel comes out with a patch/new 
BIOS?  Aside from shutting the system off and using wake on lan?

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ