lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200707171741.27628.ak@suse.de>
Date:	Tue, 17 Jul 2007 17:41:27 +0200
From:	Andi Kleen <ak@...e.de>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Aaron Durbin <adurbin@...gle.com>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, len.brown@...el.com, akpm@...l.org
Subject: Re: [PATCH] ACPI: Add reboot mechanism

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
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ