Plymouth crashes on boot about 1 out of 3 times.

[ron.neville]

Sometimes X server crashes first?
See 1007183.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu30
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: kp_malibu_module windrvr6
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 31 15:53:17 2012
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=8f027b32-c911-493e-b82e-46ee9095d3d6 ro quiet splash vt.handoff=7
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=8f027b32-c911-493e-b82e-46ee9095d3d6 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: HURONRIVER
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/12/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Steve Langasek (vorlon)]

Please elaborate. What do you mean by "crash"?

[ron.neville (ron-neville)]

There is a file "_sbin_plymouthd.0.crash" in /var/crash.

When the system does successfully boot,
running ubuntu-bug from the command line gives me the opportunity to create this bug.

Sometime our systems with this hardware and software combo boot OK.

Sometimes we get a black screen.

Sometimes we get a black screen with a mouse cursor.

Sometimes we get a text login prompt.
After a text login, sometimes "startx" will work, sometimes not.

Sometimes we get GRUB menu (I think this is from GRUB failure recovery?).

Sometimes we get
"mountall: Disconnected from Plymouth"
Pressing enter at this point allows the system to boot.

We are reviewing all the system logs trying to determine the cause
(or at least a work-around).

See also #1007183 (Xorg crash)

[Steve Langasek (vorlon)]

On Fri, Jun 01, 2012 at 12:53:08AM -0000, ron.neville wrote:
> There is a file "_sbin_plymouthd.0.crash" in /var/crash.

We will need the contents of this file to understand the issue you're
experiencing.

[ron.neville (ron-neville)]

Attaching plymouth crash file.

[ron.neville (ron-neville)]

Attaching syslog

[Steve Langasek (vorlon)]

The stacktrace within the apport report shows the following:

#0 0x00007f168acac445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1 0x00007f168acafbab in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2 0x00007f168aca510e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#3 0x00007f168aca51b2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#4 0x00007f16896f92c4 in drm_intel_bufmgr_gem_init () from /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1
No symbol table info available.
#5 0x00007f1689911f1c in ?? () from /lib/plymouth/renderers/drm.so
No symbol table info available.
#6 0x00007f1689911aea in ?? () from /lib/plymouth/renderers/drm.so
No symbol table info available.
#7 0x00007f168b03c8be in ply_renderer_open () from /lib/libply-splash-core.so.2
No symbol table info available.

This points to an issue in the drm driver. Reassigning.

[ron.neville (ron-neville)]

This "patch" pulled out of the archives for similar issues

echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/splash
update-initramfs -u

appears to prevent the problem.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Timo Aaltonen (tjaalton)]

in case you've upgraded to a newer release since, have you been able to reproduce this crash?

[Launchpad Janitor (janitor)]

[Expired for libdrm (Ubuntu) because there has been no activity for 60 days.]