public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bruno Friedmann <bruno@ioda-net.ch>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Mel Gorman <mgorman@suse.de>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Add reboot quirk for Dell Precision M4600
Date: Tue, 09 Aug 2011 18:20:07 +0200	[thread overview]
Message-ID: <4E415E37.2060107@ioda-net.ch> (raw)
In-Reply-To: <20110809150224.GF28228@elte.hu>

On 08/09/2011 05:02 PM, Ingo Molnar wrote:
> 
> * Bruno Friedmann <bruno@ioda-net.ch> wrote:
> 
>> On 08/08/2011 06:40 PM, H. Peter Anvin wrote:
>>> On 08/06/2011 10:30 AM, Matthew Garrett wrote:
>>>> On Sat, Aug 06, 2011 at 08:56:35AM +0200, Ingo Molnar wrote:
>>>>> Weird - ACPI is the default Windows method of reboot - how come it 
>>>>> does not work on that box? Does Windows work around this specific 
>>>>> machine (unlikely), or is our ACPI boot sequence not 100% compatible 
>>>>> with the Windows method (more likely IMO)?
>>>>
>>>> The ACPI reboot method on these machines hits the keyboard controller 
>>>> rather than PCI, which is unusual. What I suspect is that the write 
>>>> triggers some SMM or EC code that's making assumptions about system 
>>>> state, and we're not quite identical. Bouncing on the keyboard 
>>>> controller from userspace with init=/bin/bash wedges in the same way.
>>>>
>>>
>>> I have a vague suspicion that Windows might have a meta-quirk for this
>>> class of machines, i.e. if the ACPI reboot method, say, points at the
>>> keyboard controller or points at the "PCI" reboot port then it actually
>>> uses its own special-purpose routines rather than general routines.  It
>>> would be extremely interesting to know if "reboot=kbd" works on these boxen.
>>>
>>> 	-hpa
>>>
>>
>> Test done with reboot=pci and unfortunately doesn't work.
> 
> Didn't hpa suggest reboot=kbd?
> 
> Thanks,
> 
> 	Ingo

Ingo yeap and reboot=kbd doesn't work ...
I must really be awake before writing

Once the system has synchronised the harddrive, it just stay at now rebooting ...


-- 

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador
GPG KEY : D5C9B751C4653227
irc: tigerfoot

  reply	other threads:[~2011-08-10 12:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 12:56 [PATCH] x86: Add reboot quirk for Dell Precision M4600 Mel Gorman
2011-08-06  6:56 ` Ingo Molnar
2011-08-06  7:01   ` H. Peter Anvin
2011-08-06 15:31     ` Len Brown
2011-08-06 18:18       ` Bruno Friedmann
2011-08-06 15:30   ` Matthew Garrett
2011-08-08 16:40     ` H. Peter Anvin
2011-08-08 22:49       ` Bruno Friedmann
2011-08-09 11:26       ` Bruno Friedmann
2011-08-09 15:02         ` Ingo Molnar
2011-08-09 16:20           ` Bruno Friedmann [this message]
2011-08-08 14:57   ` Mel Gorman

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=4E415E37.2060107@ioda-net.ch \
    --to=bruno@ioda-net.ch \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --cc=tglx@linutronix.de \
    /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