Re: [patch/rft 2.6.17-rc2] swsusp resume must not device_suspend()

Pavel Machek
2006-04-27T08:08:27Z

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

Hi!

> The right way to solve this is to make sure that the resuming kernel can
> correctly determine whether the power session (way back from the original
> sw-suspend) is still intact. It's expected that in many cases it won't
> be, because most systems won't provide suspend current while the machine
> is off. We have to guarantee that the boot kernel's actions won't end up
> fooling the resuming kernel into thinking that the power sessions are
> intact when in fact they aren't. (Furthermore, in an ideal world, we
> would also make sure that the boot kernel won't destroy any power sessions
> that still _are_ intact. Right now we have no way to do this, because the
> drivers in the boot kernel don't know that it _is_ a boot kernel.)

You don't know if it is boot or resume until you read the disk, sorry.

Pavel
--
Thanks, Sharp!

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]