Ubuntu
plymouth package

plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #920396 reported by T Loften on 2012-01-23

This bug report is a duplicate of: Bug #553745: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events(). Edit Remove

262

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	plymouth (Ubuntu)	New	Undecided	Unassigned

Bug Description

after login, receive Kernel crash ( 3.2.0- 10- ), then plymounth crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Jan 23 05:32:21 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120120)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: NOTEBOOK SAM2000
PccardctlIdent:
Socket 0:
   no product info available
Socket 1:
   no product info available
PccardctlStatus:
Socket 0:
   no card
Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=6fa4f42e-deca-4e8b-9a24-905906f6e10a ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=6fa4f42e-deca-4e8b-9a24-905906f6e10a ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7fc47ffa3504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
PC (0x7fc47ffa3504) ok
source "%r12d" ok
destination "0x8(%r13)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_event_loop_process_pending_events () from /lib/libply.so.2
ply_event_loop_run () from /lib/libply.so.2
?? ()
__libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: Upgraded to precise on 2012-01-22 (0 days ago)
UserGroups:

dmi.bios.date: 09/12/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1013AG6 V6.10
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1013AG6V6.10:bd09/12/2005:svnNOTEBOOK:pnSAM2000:pvr0131:cvnMICRO-STARINT'LCO.,LTD:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: SAM2000
dmi.product.version: 0131
dmi.sys.vendor: NOTEBOOK

Tags:

Revision history for this message

T Loften (tloften) wrote on 2012-01-23:

BootDmesg.txt Edit (52.3 KiB, text/plain; charset="utf-8")
BootLog.gz Edit (620 bytes, application/x-gzip)
CurrentDmesg.txt Edit (4.2 KiB, text/plain; charset="utf-8")
EtcDefaultGrub.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (586 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (914 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (92.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (220.1 KiB, text/plain; charset="utf-8")

crash log Edit (2.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-23: 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 #849414, 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.