Comment 10 for bug 1192051

Oops, I forgot to post my original findings here. You might find them helpful...

plymouthd is spinning on an fd of "/dev/tty7" with errno==EIO. Waiting for the "plymouth deactivate" to properly complete (hence drmDropMaster), avoids the bug.

So it looks like plymouth's DRM code is not very clever with its error handling. Once it starts getting EIO it should probably give up. Instead, it doesn't understand EIO and retries constantly.

Also, enhancing plymouth so that "plymouth --wait" works with the deactivate command would have been very helpful. Right now, plymouth --wait does not wait for the deactivate to complete.