linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Robert Hancock <hancockrwd@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:27:22 -0700	[thread overview]
Message-ID: <4C06F6EA.6090701@gmail.com> (raw)
In-Reply-To: <AANLkTilQuun1jQc394YM4QZtDSVeIwh67_Np0mkRDes4@mail.gmail.com>

On 06/02/2010 05:20 PM, Robert Hancock wrote:
> On Wed, Jun 2, 2010 at 6:05 PM, Justin P. Mattock
> <justinmattock@gmail.com>  wrote:
>>>>> 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?
>>>
>>
>> my bad(tired)I left out iopl(3);
>> in the code which was giving a segfault.
>>
>> running the below code(s) just gives a command prompt
>>
>> int main() {
>>         iopl(3);
>>         outb(0xfe, 0xcf9);
>>         return 0;
>> }
>>
>> int main() {
>>         iopl(3);
>>         outb(6, 0xcf9);
>>         return 0;
>> }
>
> What if you do:
>
> #include<unistd.h>
>
> int main() {
>          iopl(3);
>          outb(2, 0xcf9);
>          sleep(1);
>          outb(6, 0xcf9);
>          return 0;
> }
>
> That's basically what PCI reboot does.
>
> It's possible it doesn't take the first time - you could try modifying
> drivers/acpi/reboot.c to call acpi_reset in a loop instead of just
> trying once (assuming you have the patch to default to ACPI reboot
> enabled).
>

the above code reboot's the machine as it should..
I can look at that(need to take a break first though)
and see..

what about the whole kbd mechanism(0x64) give the info I provided
does it look possible, or is this machine strictly on cf9?

cheers,

Justin P. Mattock

  reply	other threads:[~2010-06-03  0:27 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
2010-06-03  0:05                                           ` Justin P. Mattock
2010-06-03  0:20                                             ` Robert Hancock
2010-06-03  0:27                                               ` Justin P. Mattock [this message]
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=4C06F6EA.6090701@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=hancockrwd@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).