plymouthd crashed with SIGSEGV in __libc_start_main()

Bug #969492 reported by calin

This bug report was converted into a question: question #192549: plymouthd crashed with SIGSEGV in __libc_start_main().

10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This is an automatic report, but I did have problems with recent versions of Ubuntu: 12.04 and 11.10 starting with kernel 3.0.0-16
I'm not sure if it is plymouth package or the kernel.
The system hangs on startup with a blank screen or blinking cursor without anything else being displayed, but not on every startup.
Kernel 3.0.0-15 worked fine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 2.0-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Mar 30 21:19:48 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=5abe7260-d8ba-48a7-b9fc-0ccce3f5e6be ro
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=5abe7260-d8ba-48a7-b9fc-0ccce3f5e6be ro
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/12/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: 00000000
dmi.board.name: K8SLI-eSATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd06/12/2006:svn:pnK8SLI-eSATA2:pvr1.00:rvn:rnK8SLI-eSATA2:rvr1.00:
dmi.product.name: K8SLI-eSATA2
dmi.product.version: 1.00

Revision history for this message
calin (c-demian) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #938971, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
calin (c-demian) wrote :

 I think it's the kernel. Booting vmlinuz-3.2.0-21-generic-pae freezes with the following lines displayed (kernel options 'ro'), also in recovery mode:

[ 0.163998] pci 0000:00:11.0: PCI bridge to [bus 05-05]
[ 0.163998] pci 0000:00:01.0: PCI INT A -> GSI 29 (level, low) -> IRQ 29
[ 0.163998] pci 0000:00:01.0: setting latency timer to 64
[ 0.163998] pci 0000:00:02.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34
[ 0.163998] pci 0000:00:02.0: setting latency timer to 64
[ 0.163998] pci 0000:00:03.0: PCI INT A -> GSI 39 (level, low) -> IRQ 39
[ 0.163998] pci 0000:00:03.0: setting latency timer to 64
[ 0.163998] pci 0000:00:04.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
[ 0.163998] pci 0000:00:04.0: setting latency timer to 64
[ 0.163998] pci 0000:00:11.0: setting latency timer to 64
[ 0.163998] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
[ 0.163998] pci_bus 0000:00: resource 5 [mem 0x40000000-0xfcffffffff]
[ 0.163998] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.163998] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
[ 0.163998] pci_bus 0000:01: resource 1 [mem 0xdef00000-0xdeffffff]
[ 0.163998] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff pref]
[ 0.163998] pci_bus 0000:02: resource 2 [mem 0xddd00000-0xdddfffff pref]
[ 0.163998] pci_bus 0000:03: resource 2 [mem 0xdde00000-0xddefffff pref]
[ 0.163998] pci_bus 0000:04: resource 2 [mem 0xddf00000-0xddffffff pref]
[ 0.163998] NET: Registered protocol family 2
[ 0.163998] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.163998] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.163998] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.163998] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.163998] TCP reno registered
[ 0.163998] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.163998] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.164193] NET: Registered protocol family 1
[ 0.164276] pci 0000:00:00.0: Enabling HT MSI Mapping
[ 0.164352] pci 0000:00:01.0: Enabling HT MSI Mapping
[ 0.164424] pci 0000:00:02.0: Enabling HT MSI Mapping
[ 0.164494] pci 0000:00:03.0: Enabling HT MSI Mapping
[ 0.164565] pci 0000:00:04.0: Enabling HT MSI Mapping
[ 0.164657] pci 0000:00:13.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.244025] pci 0000:00:13.0: PCI INT A disabled
[ 0.244090] pci 0000:00:13.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18

Revision history for this message
calin (c-demian) wrote :

Please recheck if the bug is really a duplicate of 938971, I can't see the first bug because it's private.

Revision history for this message
calin (c-demian) wrote :

I have a boot problem (system hangs at startup). The bug was reported automatically after system start and I'm not sure it's related to the boot hang issue. Should I report a new bug? Thank you.

Changed in plymouth (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.