swsusp & modules [was Re: [linux-pm] [Fwd: Re: PM messages]]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

> Actually the point I've been meaning to chime in on here is
> that since, as Benjamin noted, if there's a "write to storage"
> step (STD, not STR) it uses the "quiesced"/"frozen" system
> state ... then the real problem is just that the current
> framework **resumes way too many devices** when writing that
> out to swap.  (Which is a fourth step...)

It unfreezes all devices. And that's right thing to do, because
otherwise you'd need to be able to tell dependencies between devices.

Imagine suspending to usb flashdisk... (Perhaps I'm paranoid and do
not want my passwords on magnetic media).

You'll pretty much need to resume everything to handle that.

Ouch and if you powerdown vga in "freeze" phase, user sees no progress and
debugging swsusp is now impossible.


				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         



[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux