From owner-freebsd-acpi@freebsd.org Thu Sep 17 08:52:39 2015 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2794D9CEB3E for ; Thu, 17 Sep 2015 08:52:39 +0000 (UTC) (envelope-from dan@obluda.cz) Received: from smtp1.ms.mff.cuni.cz (smtp1.ms.mff.cuni.cz [IPv6:2001:718:1e03:801::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6BFA3141A; Thu, 17 Sep 2015 08:52:38 +0000 (UTC) (envelope-from dan@obluda.cz) X-SubmittedBy: id 100000045929 subject /C=CZ/O=Univerzita+20Karlova+20v+20Praze/CN=Dan+20Lukes/unstructuredName=100000045929 issued by /C=NL/ST=Noord-Holland/L=Amsterdam/O=TERENA/CN=TERENA+20Personal+20CA+202 auth type TLS.MFF Received: from [100.89.115.44] (ip-37-188-230-53.eurotel.cz [37.188.230.53]) (authenticated) by smtp1.ms.mff.cuni.cz (8.14.9/8.14.9) with ESMTP id t8H8qTYm047796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 17 Sep 2015 10:52:34 +0200 (CEST) (envelope-from dan@obluda.cz) Subject: Re: disabling sleep when shutting down To: Colin Percival , "freebsd-acpi@freebsd.org" References: <55FA3848.7090802@freebsd.org> From: Dan Lukes Message-ID: <55FA7F47.6050508@obluda.cz> Date: Thu, 17 Sep 2015 10:52:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Firefox/38.0 SeaMonkey/2.35 MIME-Version: 1.0 In-Reply-To: <55FA3848.7090802@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 08:52:39 -0000 Colin Percival wrote: > I ran into an interesting glitch recently: I told my laptop to shut down, > then closed the lid... and it promptly went into S3. When I opened the > lid a couple days later, it resumed... and then finished the shutdown > which it had started 2 days earlier. Yes, it's well known behavior to me. > I think we need to get the kernel ACPI bits to disable Suspend. I consider it is suboptimal solution. I wish the suspend still happen if shutdown will not complete for any reason. All I want is that lid close doesn't trigger any action during shutdown. So what about hw.acpi.lid_switch_state just to be set to NONE during shutdown ? Dan