http://bugzilla.suse.com/show_bug.cgi?id=1028136
http://bugzilla.suse.com/show_bug.cgi?id=1028136#c15
--- Comment #15 from Daniel Molkentin ---
A bit more detail on the subject of why there is a difference:
dracut: Executing: /usr/bin/dracut -v --logfile /var/log/YaST2/mkinitrd.log
--force /boot/initrd-4.10.3-1-default 4.10.3-1-default
vs.
dracut: Executing: /usr/bin/dracut --no-host-only -v --logfile
/var/log/YaST2/mkinitrd.log --force /boot/initrd-4.10.3-1-default
4.10.3-1-default
mkinitrd's -A actually sets --no-host-only which excludes the 95resume module.
This module tries to resume from the block device in question, and fails. So
this explains why the -A one boots fast while the other times out.
We still have to find out why 95resume adds
resume=UUID=bab51854-d247-4166-90cc-2b9041e5c199, despite there being no trace
of said UUID so far.
--
You are receiving this mail because:
You are on the CC list for the bug.