linux-kernel - Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi

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: <AANLkTinyxtHQrsgvV0CMQZnyEelVnrpCTM05PLAj-ZYx@mail.gmail.com>
Date:	Wed, 2 Jun 2010 17:18:19 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, x86@...nel.org,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table.

On Wed, Jun 2, 2010 at 12:01 AM, Justin P. Mattock
<justinmattock@...il.com> wrote:
>> Can you post the FACP section of the acpidump output from this machine?
>>
>
> here you go:
>


>             Reset Register Supported (V2) : 1

> [074h 116 12]               Reset Register : <Generic Address Structure>
> [074h 116  1]                     Space ID : 01 (SystemIO)
> [075h 117  1]                    Bit Width : 08
> [076h 118  1]                   Bit Offset : 00
> [077h 119  1]                 Access Width : 00
> [078h 120  8]                      Address : 0000000000000CF9
>
> [080h 128  1]         Value to cause reset : 06

Hmm, so the FADT says the reset register is listed as supported, and
says writing 0x06 to 0xCF9 is supposed to do it.. That's exactly what
this should do:

#include <sys/io.h>

int main() {
    iopl(3);
    outb(6, 0xcf9);
    return 0;
}

but you said that didn't do anything.. It kind of seems like ACPI
reboot is busted on this machine then, but then I wonder how Windows
manages to work..
--
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/