[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090515211517.GB22906@khazad-dum.debian.net>
Date: Fri, 15 May 2009 18:15:17 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Pavel Machek <pavel@....cz>
Cc: kernel list <linux-kernel@...r.kernel.org>,
linux-pm@...ts.linux-foundation.org, linux-acpi@...r.kernel.org
Subject: Re: suspending machine from kernel (was Re: [linux-pm] [RFC] why
do we need run disk sync before entering S3)
On Fri, 15 May 2009, Pavel Machek wrote:
> > thinkpad-acpi receives some critical alarms from the firmware, for which the
> > recommended action by the vendor is to go into S3 immediately. There is
> > also one which requires S4 as the recommended damage control measure.
>
> While s2ram should always work on hardware that supports it (zaurus),
> S4 is more tricky. It needs swap to be configured, and userspace
> cooperation in uswsusp case.
Yeah, this really calls for issuing some sort of event to userspace that has
the "emergency" connotation, so that desktop enviromnents don't start doing
retarted things like asking the user stupid questions when the machine has
30 seconds left of battery juice, or got waken up from S3 due to a
critically hot thermal alarm.
> I guess sending signal to init would be right solution in that
> case. (ACPI already does that on overheat.)
I will look into this.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists