plymouth causes a hard reset of the nexus

[Bryce Harrington]

Plymouth on the Nexus7 (tegra3) seems to kill the kernel. On the AC100 (tegra2) is just caused a black screen. We disabled plymouth in our image, but would like a better fix.

[Alex Chiang (achiang)]

ubuntu-defaults-nexus7 (0.2) quantal; urgency=low

  * rootfs/etc/init/plymouth*.override
    - do not run any plymouth jobs since they kill the kernel (LP: #1065644)

 -- Alex Chiang <email address hidden> Thu, 11 Oct 2012 21:18:39 -0700

[Chris Wayne (cwayne)]

Verified fixed

[Alex Chiang (achiang)]

We shipped a workaround in the Nexus 7 to simply avoid running plymouth at all, but that's not a proper solution.

Re-opening so we can track upstream.

[Oliver Grawert (ogra)]

the abover log uses teh following cmdline:

tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d2109ce281010 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=14934015 androidboot.bootloader=3.34 root=/dev/mmcblk0p9 ro console=tty1 fbcon=rotate:1 quiet splash plymouth:debug

seems like plymouth picks the console=none up from there, this is sadly a parameter we cant change (up to root= everything is hardcoded in the bootloader, everything from root= to the end is our cmdline supplied by the system)

i guess making plymouth ignore consoles called "none" should simply make it work for us

[Alex Chiang (achiang)]

This might not be a bug in tegra3, see LP: #1084063

[Oliver Grawert (ogra)]

someone with a quantal install should verify if the workaround from LP: #1084063 helps in quantal, it is still not clear if it is the tegrafb driver or plymouth though

[Steven Barker (steven-barker2)]

Just installed a new image on my tf201 and hit this bug. LP: #1084063 solved the problem