Date: Thu, 17 Sep 2015 23:39:38 +0200 From: Dan Lukes <dan@obluda.cz> To: Colin Percival <cperciva@freebsd.org>, Ian Smith <smithi@nimnet.asn.au> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org> Subject: Re: disabling sleep when shutting down Message-ID: <55FB331A.4010908@obluda.cz> In-Reply-To: <55FB187F.2090000@freebsd.org> References: <55FA3848.7090802@freebsd.org> <55FA7F47.6050508@obluda.cz> <20150917211219.M29510@sola.nimnet.asn.au> <55FB187F.2090000@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival wrote: > I considered that option but thought that disabling suspend completely > would be better in case it was triggered by something else You has been affected by LID issue - and here I'm with you. Suspend triggered by exhausted battery case needs to be evaluated carefully. Battery may be so exhausted so shutdown will not be completed. Note that some system (hardware) require no power to maintain suspend context, thus suspend may save system. And what about other reasons for suspends ? I can tell nothing about all those cases. Suspend may be triggered for any reason, thus so many possible causes. I can't claim all of them are illegitimate and can be safely ignored. I wish we should have stronger reason for system global behavior change than just feeling (no offense!). Just my $0.02. If system behavior will be changed, I will take it :-) Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55FB331A.4010908>