Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Sep 2015 15:12:06 -0400
From:      Jung-uk Kim <jkim@FreeBSD.org>
To:        Anthony Jenkins <Scoobi_doo@yahoo.com>, Colin Percival <cperciva@freebsd.org>, "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>
Subject:   Re: disabling sleep when shutting down
Message-ID:  <55FC6206.8080303@FreeBSD.org>
In-Reply-To: <55FC57F9.3050702@yahoo.com>
References:  <55FA3848.7090802@freebsd.org> <55FB233D.2080000@FreeBSD.org> <55FB48E3.20401@freebsd.org> <55FC4F13.3090603@FreeBSD.org> <55FC57F9.3050702@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/18/2015 14:29, Anthony Jenkins wrote:
> On 09/18/2015 01:51 PM, Jung-uk Kim wrote:
>> On 09/17/2015 19:12, Colin Percival wrote: > > On 09/17/15 13:31,
>> Jung-uk Kim wrote: > >> On 09/16/2015 23:49,
> 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. > >> > >>
> Please try the attached patch. > > > No, this doesn't do what I
> wanted.  It might be a good idea anyway, > > but your patch only
> disables suspend once the kernel is trying to > > reboot; what I
> want is to disable suspend a bit earlier -- once > > rc.shutdown is
> running and the userland is trying to shut down, > > because at
> that point unless something breaks horribly we're *about > > to*
> tell the kernel to shut down even though we haven't gotten > >
> there quite yet. > > Okay.  The attached patch is a quick-and-dirty
> & untested hack for you. > > Jung-uk Kim
> 
> Is it possible for /etc/rc.shutdown to complete, but shutdown not 
> occur?  If so, there should be a mechanism to restore the ability
> to suspend.  Other than that, I like it.

If something goes wrong, you can manually do "acpiconf -b 0".

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJV/GIBAAoJEHyflib82/FGL9EH/jLI2o2LX+8TrHY+RzwkWvq7
SEXue/Fh0wkZvwUDerqgguWDB83X3xGkP2huWkcZEQ605br9FgFBnjVu2A1sPSw+
KBh20jiggv3pEd+3uJJGp6v8Mz33HRW7Se1xCajtZhadFgbqXMT5pxXkLjELheZb
H2S2b7oStkZoSw89RLGzzX0DsakvbbXUPA4RUV7niCKPR2kSKpDqER/iY1+PGzYN
6M3EnwBNGWCxWYu+j+bMR/YqoK69DdY4RlHSRd08xleLif6LaDjOQpg/Gd22HMMR
6eEPIv96KAZbN25ZV7vmw4x8a1CrU1Glp6Lg0/Kuv0usCPfmeng1gtZZqirEr5c=
=jWfB
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55FC6206.8080303>