The question is: was the dracut update installed before you first pm-hibernated your machine to have it then show the issue? If not, the hibernate might have silently corrupted the file system in a way which did cause the kernel to crash (and even though IMO the kernel should not be allowed to crash even in case of corruption, this beast sometimes just does not do what I want it to do! :-) My guess would be that this really is the issue: you had the old dracut when hibernating for the first time. Now with the new dracut the problem is gone => bug probably fixed. A reboot into rescue and a thorough file system check on all your file systems cannot hurt, though.