Comment 21 for bug 553675

Aha, Sarvatt figured it out. He indicated around -15 there was a change to how filesystem mounting worked, and some entries in fstab could cause this boot. Once I deleted all my chroot and nfs mounts out of fstab, it came up on the -19 kernel.

So that's fine, although this is an extraordinarily unfriendly way of handling issues with fstab formatting....