Comment 89 for bug 290153

Hello.
I experienced the same problem with an ASUS A6Rp, but I can add some (hoping) useful infos: the system is unable to boot only after the sequence: suspend -> failed resume -> forced poweroff (I did not tried with hibernate).
I faced with the problem while testing suspend/resume for finding correct quirks. Adding the option rootdelay=90 I was able to boot regularly; then I tried to reboot and all worked fine without added options.
Considering that /dev/disk/by-uuid/<uuid> exists and points to correct device, maybe the problem is in some sort of inconsistent state of the controller/driver caused by failed resume (or something so).