From owner-freebsd-acpi@freebsd.org Thu Sep 17 11:31:33 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 B4A3C9CD98C for ; Thu, 17 Sep 2015 11:31:33 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (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 1BA3A19E7; Thu, 17 Sep 2015 11:31:32 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id t8HBVQnm034309; Thu, 17 Sep 2015 21:31:27 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 17 Sep 2015 21:31:26 +1000 (EST) From: Ian Smith To: Dan Lukes cc: Colin Percival , "freebsd-acpi@freebsd.org" Subject: Re: disabling sleep when shutting down In-Reply-To: <55FA7F47.6050508@obluda.cz> Message-ID: <20150917211219.M29510@sola.nimnet.asn.au> References: <55FA3848.7090802@freebsd.org> <55FA7F47.6050508@obluda.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 11:31:33 -0000 On Thu, 17 Sep 2015 10:52:23 +0200, Dan Lukes wrote: > 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. News to me, but I never suspend on lid down .. well I tested it once. > > 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 ? That sounds sensible and likely much easier to accomplish. It needs to happen early enough in shutdown to beat the fastest of lid-slammers :) cheers, Ian