[Bug 1084063] Re: plymouth in raring seems to have a race condition on the nexus7

[Oliver Grawert]

worked around in ubuntu-defaults-nexus7 through setting FRAMEBUFFER=y ... 
(it would still be good to know why plymouth needs console_setup to run on this hardware)

** Also affects: ubuntu-defaults-nexus7 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
       Status: New => In Progress

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Also affects: plymouth (Ubuntu Raring)
   Importance: High
       Status: New

** Also affects: ubuntu-defaults-nexus7 (Ubuntu Raring)
   Importance: High
     Assignee: Oliver Grawert (ogra)
       Status: In Progress

** Summary changed:

- plymouth in raring seems to have a race condition on the nexus7
+ plymouth in raring causes system hardlock if console_setup is not run in the initramfs on nexus7 prior to starting plymouthd

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1084063

Title:
  plymouth in raring causes system hardlock if console_setup is not run
  in the initramfs on nexus7 prior to starting plymouthd

Status in “plymouth” package in Ubuntu:
  New
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  In Progress
Status in “plymouth” source package in Raring:
  New
Status in “ubuntu-defaults-nexus7” source package in Raring:
  In Progress

Bug description:
  while i can see the splash fine if i add a break= statement to my kernel commandline and manually ctrl-d out of the initrd shell, 
  using plymouth without a break statement causes a hard reboot of the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1084063/+subscriptions