linux-kernel - Re: Machine reboot

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]

Message-ID: <20061013232248.83292.qmail@web83107.mail.mud.yahoo.com>
Date:	Fri, 13 Oct 2006 16:22:48 -0700 (PDT)
From:	Aleksey Gorelov <dared1st@...oo.com>
To:	Auke Kok <auke-jan.h.kok@...el.com>,
	Lukas Hejtmanek <xhejtman@...l.muni.cz>
Cc:	ryan@....solarneutrino.net, linux-kernel@...r.kernel.org,
	magnus.damm@...il.com, pavel@...e.cz
Subject: Re: Machine reboot

--- Auke Kok <auke-jan.h.kok@...el.com> wrote:

> > 
> > For i965 chipsets, the BIOS is *a lot* buggy :(
> 
> that's depressing, can you send me the output of `dmidecode` of the latest BIOS? Perhaps 
> I can reproduce it myself with that version.
> 
Hi, Auke

 It looks like the reason for reboot failure is unability of BIOS to reboot if network pci device
is in D3 state. Once I've added 
 	pci_set_power_state(pdev, PCI_D0);
as a last line to e1000_shutdown() method, board started rebooting again.
Moreover, here is what I found in release notes to the latest BIOS (from October 5, 2006):
"Fixed an issue where system not able to shutdown to S5 if the LAN is set to D3 mode."
This may have affected reboot with LAN in D3 negatively.
  I guess you are in the best position of all of us to bring the issue to Intel BIOS team. 

Aleks.

-
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/