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. -- Anthony Jenkins _______________________________________________ freebsd-acpi@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
