From: Robert Hancock <hancockrwd@gmail.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
x86@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table.
Date: Wed, 02 Jun 2010 17:45:28 -0600 [thread overview]
Message-ID: <4C06ED18.2010400@gmail.com> (raw)
In-Reply-To: <4C06ECAA.3060708@gmail.com>
On 06/02/2010 05:43 PM, Justin P. Mattock wrote:
> On 06/02/2010 04:18 PM, Robert Hancock wrote:
>> On Wed, Jun 2, 2010 at 12:01 AM, Justin P. Mattock
>> <justinmattock@gmail.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..
>>
>
>
> alright!! I have a better idea at what this is now..
> as for the above code, yes this one segfaults,
> the other code posted on the thread just returns
> a command prompt(testing:
You get a segfault on that one? Running as root?
>
> #include <sys/io.h>
>
> int main() {
> iopl(3);
> outb(0xfe, 0xcf9);
> return 0;
> }
> on a dell reboot's as is.)
>
> both my macbook, and imac are
> broken with the above.(but for whatever
> reason the macbook doesnt need an dmi entry
> in reboot.c just iMac9,1 etc..)
>
> so the address for the CF9 is this:
>
> [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
> [081h 129 3] Reserved : 000000
> [084h 132 8] FACS Address : 00000000BFECD000
> [08Ch 140 8] DSDT Address : 00000000BFEE0000
> [094h 148 12] PM1A Event Block : <Generic Address Structure>
> [094h 148 1] Space ID : 01 (SystemIO)
> [095h 149 1] Bit Width : 20
> [096h 150 1] Bit Offset : 00
> [097h 151 1] Access Width : 00
> [098h 152 8] Address : 0000000000000400
>
> not sure how to read this, but are there
> two devices here i.g.
> is the top a cold boot(reset register) and
> the bottom(value to cause reset) a warm boot?
No, the stuff after "Value to cause reset" is something else entirely.
>
> at the moment I'm trying to figure out what/where
> *((unsigned short *)__va(0x472)) = reboot_mode;
> 0x472 comes from as well as 0x1234 then
> #define KBD_STATUS_REG 0x64
> to see if I can see anything.
>
>
> thanks for the info on this..
>
> Justin P. Mattock
>
next prev parent reply other threads:[~2010-06-02 23:45 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 6:26 [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table Justin P. Mattock
2010-05-31 17:07 ` Matthew Garrett
2010-05-31 17:46 ` Justin P. Mattock
2010-06-01 19:00 ` Matthew Garrett
2010-06-01 19:14 ` Justin P. Mattock
2010-06-01 19:21 ` Matthew Garrett
2010-06-01 20:06 ` Justin P. Mattock
2010-06-01 20:07 ` Matthew Garrett
2010-06-01 20:17 ` Justin P. Mattock
2010-06-01 20:21 ` Matthew Garrett
2010-06-01 20:31 ` Justin P. Mattock
2010-06-01 20:33 ` Matthew Garrett
2010-06-01 20:51 ` Justin P. Mattock
2010-06-01 21:12 ` Matthew Garrett
2010-06-01 21:26 ` Justin P. Mattock
2010-06-01 21:29 ` Matthew Garrett
2010-06-01 21:43 ` Justin P. Mattock
2010-06-01 21:48 ` Matthew Garrett
2010-06-01 21:56 ` Justin P. Mattock
2010-06-02 12:08 ` Alan Cox
2010-06-02 13:32 ` Justin P. Mattock
2010-06-02 5:11 ` Robert Hancock
2010-06-02 6:01 ` Justin P. Mattock
2010-06-02 23:18 ` Robert Hancock
2010-06-02 23:43 ` Justin P. Mattock
2010-06-02 23:45 ` Robert Hancock [this message]
2010-06-03 0:05 ` Justin P. Mattock
2010-06-03 0:20 ` Robert Hancock
2010-06-03 0:27 ` Justin P. Mattock
2010-06-03 0:34 ` Robert Hancock
2010-06-03 0:51 ` Justin P. Mattock
2010-06-03 1:37 ` Matthew Garrett
2010-06-03 1:46 ` Justin P. Mattock
2010-06-03 1:47 ` Robert Hancock
2010-06-03 1:56 ` Matthew Garrett
2010-06-03 2:06 ` Justin P. Mattock
2010-06-03 2:06 ` Robert Hancock
2010-06-03 2:00 ` Justin P. Mattock
2010-06-03 2:05 ` Robert Hancock
2010-06-03 2:16 ` Justin P. Mattock
2010-06-03 2:15 ` Justin P. Mattock
2010-06-03 2:18 ` Matthew Garrett
2010-06-03 2:22 ` Justin P. Mattock
2010-06-03 9:54 ` Alan Cox
2010-06-03 10:11 ` Justin P. Mattock
2010-06-03 11:46 ` Matthew Garrett
2010-06-03 14:43 ` Robert Hancock
2010-06-03 2:19 ` Justin P. Mattock
2010-07-31 19:00 ` Justin Mattock
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=4C06ED18.2010400@gmail.com \
--to=hancockrwd@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).