On 10/02/2018 09:16 AM, Bastien Nocera wrote:
----- Original Message -----
> On Di, 02.10.18 10:16, Bastien Nocera (bnocera(a)redhat.com) wrote:
>> Until the kernel can use a dedicated partition for hibernation, which
>> would fix the majority of problems users can encounter, we're just
>> offering more sharp edges with which to cut themselves.
> As I understand the problems have more to do with hardware
> combinations, and driver code not getting things right, the actual
> serialization of stuff is fine and unproblematic...
There's problems with:
- not having enough swap space available at a particular instant
- swap being encrypted and not allowing restore because the keys aren't
- swap not being encrypted, which could leak information down the line
- resume= not being there in the default parameters, so dracut needing
to rewrite the initrd before hibernation is considered done (?)
If the drivers being broken were the only problem, then reporting bugs upstream
for those drivers would help, just in the same way it helped for suspend
10 years ago.
In my experience, the problem isn't so much with specific drivers, and
more with the whole infrastructure, whether in the kernel, user-space,
or a combination of both.
This is the real objection I have: hibernation ultimately has many
different parts and just disabling at the kernel level misses some
important pieces. It's not clear to me if just allowing users to
enable kernel support on the command line will be enough to have
a good end user experience.