@juliank This does not appear to be a complete fix for the issue seen on AWS t2.nano. I see failures in about 5 - 10% of cases. There are two different symptoms:
* grub-initrd-fallback.service sometimes runs right before the system hibernates (it runs after the hibernation request was sent to the VM and before it and before it fully hibernates). * grub-initrd-fallback.service sometimes runs after resume, but checking the status of `initrdfail` a few minutes later indicates it is still set (not sure if it was ever cleared). Both of these were determined by checking the last active timestamp reported by 'systemctl status grub-initrd-fallback.service' and comparing this with timestamps generated by the hibernation test. If either situation occurs, the next hibernation/resume will fail. I'm trying to collect more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929860 Title: initrdfail can result in resuming with different initrd images and hanging resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
