I don't think this is going to be hardware specific. Peering through the source code for mountall I think there may be at least one failure case that is not handled. If plymouth dies after the first connection to it is made the failure will be reported every time progress is supposed to be updated. Perhaps it should be reported only the first time?
I'm not quite sure why mountall is not spotting the fsck has quit. This is surprisingly difficult to debug too... -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
