Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756848Ab1FVLWc (ORCPT ); Wed, 22 Jun 2011 07:22:32 -0400 Received: from lemon.ertos.nicta.com.au ([203.143.174.143]:58895 "EHLO lemon.ken.nicta.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753372Ab1FVLWb (ORCPT ); Wed, 22 Jun 2011 07:22:31 -0400 X-Greylist: delayed 1797 seconds by postgrey-1.27 at vger.kernel.org; Wed, 22 Jun 2011 07:22:30 EDT Date: Wed, 22 Jun 2011 20:38:08 +1000 Message-ID: From: Peter Chubb To: mjg@redhat.com CC: linux-kernel@vger.kernel.org User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/23.3 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-Face: GgFg(Z>fx((4\32hvXq<)|jndSniCH~~$D)Ka:P@e@JR1P%Vr}EwUdfwf-4j\rUs#JR{'h# !]])6%Jh~b$VA|ALhnpPiHu[-x~@<"@Iv&|%R)Fq[[,(&Z'O)Q)xCqe1\M[F8#9l8~}#u$S$Rm`S9% \'T@`:&8>Sb*c5d'=eDYI&GF`+t[LfDH="MP5rwOO]w>ALi7'=QJHz&y&C&TE_3j! Organization: National ICT Australia MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 220.239.163.170 X-SA-Exim-Mail-From: peter.chubb@nicta.com.au Subject: Acer Aspire One now hangs on reboot/shutdown X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:11 +0000) X-SA-Exim-Scanned: Yes (on lemon.ken.nicta.com.au) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1245 Lines: 30 Hi Matthew, GIT commit 660e34cebf0a11d54f2d5dd8838607452355f321 x86: reorder reboot method preferences causes my Acer Aspire One to hang on shutdown/reboot. I'm running the original Aspire One A110, BIOS version 3310. Booting with reboot=k or reboot=b both work; so it looks like an ACPI firmware bug. I printed out the FADT bits that were relevant---it claims revision 4 in the header, and the ACPI_FADT_RESET_REGISTER bit is set in the flags. The values of the reset register's address and width look reasonable (address 3321 in IO space, width 8 offset 0) I'm not sure of the best fix: one could I suppose add the Aspire One to the list of machines that need BIOS reboot. Is there a cleaner fix? Peter C -- Dr Peter Chubb peter DOT chubb AT nicta.com.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia All things shall perish from under the sky/Music alone shall live, never to die -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/