[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTin-x9bkzWO6jgKd4dbB10uzhbJQUlN9rnGnFHFI@mail.gmail.com>
Date: Thu, 3 Jun 2010 08:43:11 -0600
From: Robert Hancock <hancockrwd@...il.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@...f.ucam.org>,
"Justin P. Mattock" <justinmattock@...il.com>, 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 Thu, Jun 3, 2010 at 3:54 AM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Thu, 3 Jun 2010 03:18:51 +0100
> Matthew Garrett <mjg59@...f.ucam.org> wrote:
>
>> On Wed, Jun 02, 2010 at 07:15:36PM -0700, Justin P. Mattock wrote:
>> > as soon as I change:
>> >
>> > int main() {
>> > iopl(3);
>> > outb(6, 0xcf9);
>> > usleep(100);
>> > outb(6, 0xcf9);
>> > return 0;
>> > }
>> > (the above gave a command prompt
>> > with numerous tries)
>>
>> Ok, so it's not that straghtforward. Sigh. There's various hacky
>> workarounds we could do here, but Windows doesn't seem to do them so I
>> lean towards suspecting that there's something wrong with our keyboard
>> controller reboot mechanism. I'll try doing some more tracing.
>
> At least some PCs you need to issue the reboot outb calls on the boot
> processor so the userspace tests won't be reliable.
In that case you could presumably run them:
taskset 0x00000001 (program name)
and see if that changes anything.
--
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