From: Andi Kleen <ak@suse.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Aaron Durbin <adurbin@google.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, akpm@osdl.org
Subject: Re: [PATCH] ACPI: Add reboot mechanism
Date: Tue, 17 Jul 2007 17:41:27 +0200 [thread overview]
Message-ID: <200707171741.27628.ak@suse.de> (raw)
In-Reply-To: <469CD4B8.9070506@shaw.ca>
On Tuesday 17 July 2007 16:39:52 Robert Hancock wrote:
> Andi Kleen wrote:
> > On Monday 16 July 2007 20:00:19 Aaron Durbin wrote:
> >> Add the ability to reset the machine using the RESET_REG in ACPI's FADT table.
> >
> > Why? I had such a patch at some point as experiment, but it never
> > helped actually fix a box.
>
> Depends if Windows resets using this method,> in that case using it as
> well would likely prevent the steady trickle of machines that seem to
> have trouble with other reset methods and need blacklist entries..
It's not that easy -- there are different windows versions out who
do different things. Sometimes systems are built for older windows
versions, sometimes systems are built for newer windows versions.
They don't necessarily work on newer versions.
But people expect Linux to run on all of them.
> I sometimes think that with these sorts of things where basic
> functionality like reboot is broken,
I'm not aware of that many systems where reboot doesn't work.
Also I'm sure there are some who don't reboot even in Windows.
Another reason is probably that reboot is quite hard to debug.
One recently new problem is that some systems don't have keyboard
controllers anymore so that method obviously doesn't work. But
it doesn't hurt to try it first because it's unlikely to break
something
The triple fault fallback is normally quite reliable though.
I would expect that putting the ACPI method in the middle
is probably safe enough.
-Andi
next prev parent reply other threads:[~2007-07-17 15:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.IMXKKgfBkv/U+MG0xx5sLkpV2Ws@ifi.uio.no>
[not found] ` <fa.+iOE+OqrQUbecN788fV4aEhLLtg@ifi.uio.no>
2007-07-17 14:39 ` [PATCH] ACPI: Add reboot mechanism Robert Hancock
2007-07-17 15:41 ` Andi Kleen [this message]
2007-07-16 18:00 Aaron Durbin
2007-07-16 18:17 ` Arjan van de Ven
2007-07-16 18:22 ` Aaron Durbin
2007-07-17 1:46 ` Shaohua Li
2007-07-17 2:10 ` Aaron Durbin
2007-07-17 11:31 ` Andi Kleen
2007-07-17 14:40 ` Yinghai Lu
2007-07-17 15:08 ` Aaron Durbin
2007-07-17 15:42 ` Andi Kleen
2007-07-17 15:47 ` Aaron Durbin
2007-07-17 15:08 ` Aaron Durbin
2007-07-27 6:17 ` Pavel Machek
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=200707171741.27628.ak@suse.de \
--to=ak@suse.de \
--cc=adurbin@google.com \
--cc=akpm@osdl.org \
--cc=hancockr@shaw.ca \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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