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

Bug #1084063 reported by Oliver Grawert on 2012-11-28
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Plymouth
Invalid
Undecided
Unassigned
ubuntu-nexus7
Undecided
Oliver Grawert
plymouth (Ubuntu)
Critical
Unassigned
Raring
Critical
Unassigned
ubuntu-defaults-nexus7 (Ubuntu)
Critical
Unassigned
Raring
Critical
Unassigned

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.

Oliver Grawert (ogra) on 2012-11-28
Changed in plymouth (Ubuntu):
importance: Undecided → High
Oliver Grawert (ogra) wrote :

doing some research it seems the panic() function that is called by maybe_break in the initramfs scripts executes /scripts/panic/console_setup. calling /scripts/panic/console_setup from /init right before the run-init execution makes boots without break= possible and fixes the splash (well, apart from it being in portrait mode despite the tty being in landscape, but thats a different bug)

Oliver Grawert (ogra) wrote :

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)

Changed in ubuntu-defaults-nexus7 (Ubuntu):
importance: Undecided → High
status: New → In Progress
assignee: nobody → Oliver Grawert (ogra)
summary: - 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
Changed in ubuntu-nexus7:
status: New → Confirmed
Changed in plymouth (Ubuntu Raring):
status: New → Triaged
Changed in ubuntu-defaults-nexus7 (Ubuntu Raring):
importance: High → Critical
Changed in ubuntu-nexus7:
assignee: nobody → Oliver Grawert (ogra)
Changed in plymouth (Ubuntu Raring):
assignee: nobody → Oliver Grawert (ogra)
importance: High → Critical
jura (zinlun) on 2013-01-06
Changed in ubuntu-nexus7:
status: Confirmed → Fix Committed
Changed in plymouth (Ubuntu Raring):
status: Triaged → Fix Committed
status: Fix Committed → Fix Released
Changed in ubuntu-defaults-nexus7 (Ubuntu Raring):
status: In Progress → Fix Released
jura (zinlun) on 2013-01-06
Changed in ubuntu-nexus7:
status: Fix Committed → Fix Released
Oliver Grawert (ogra) wrote :

please do not randomly set bug statuses to fix-released without poining to the actual upload that fixed the issue ...
this particular bug is not fixed yet, it just has a workaround.

Changed in plymouth (Ubuntu Raring):
status: Fix Released → In Progress
Changed in ubuntu-defaults-nexus7 (Ubuntu Raring):
status: Fix Released → In Progress
tags: added: mobile nexus7
tags: added: raring
swestlake (westlake2012) on 2013-03-11
information type: Public → Public Security
information type: Public Security → Public
coin123 (bkz1986) on 2013-05-21
description: updated
Oliver Grawert (ogra) on 2014-09-29
Changed in plymouth (Ubuntu):
assignee: Oliver Grawert (ogra) → nobody
Changed in plymouth (Ubuntu Raring):
assignee: Oliver Grawert (ogra) → nobody
Changed in ubuntu-defaults-nexus7 (Ubuntu):
assignee: Oliver Grawert (ogra) → nobody
Changed in ubuntu-defaults-nexus7 (Ubuntu Raring):
assignee: Oliver Grawert (ogra) → nobody
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in plymouth (Ubuntu Raring):
status: In Progress → Won't Fix
Changed in ubuntu-defaults-nexus7 (Ubuntu Raring):
status: In Progress → Won't Fix
Oliver Grawert (ogra) wrote :

ubuntu-defaults-nexus7 is long gone from the archive ... invalidating the bug task for it

Changed in ubuntu-defaults-nexus7 (Ubuntu):
status: In Progress → Invalid
Steve Langasek (vorlon) on 2015-03-30
Changed in plymouth:
status: New → Invalid
nathan (nathan95-b) on 2016-01-06
Changed in plymouth (Ubuntu):
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers