Comment 1 for bug 519735

What hardware is this on?

Unfortunately I can't even attempt to reproduce this with my system here because I have crypted root so have to type in a passphrase at boot time, but I suspect this is a hardware-specific kernel problem rather than a plymouth bug.