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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
