plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #906156 reported by Carl Karsten
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have been rebooting the machine every minute for a few hours, logging some firewire data. might be relevant. log filled up?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Sun Dec 18 19:31:26 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=b5c83a0b-baed-4a8b-a828-b65be5fe3d29 ro firewire-ohci.debug=3
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=b5c83a0b-baed-4a8b-a828-b65be5fe3d29 ro firewire-ohci.debug=3
SegvAnalysis:
 Segfault happened at: 0x7f5783b47504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f5783b47504) 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 (main=0x403830, argc=3, ubp_av=0x7fff99b2feb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff99b2fea8) at libc-start.c:226
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/11/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.27
dmi.board.name: 30CF
dmi.board.vendor: Quanta
dmi.board.version: 85.24
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd01/11/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30CF:rvr85.24:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Carl Karsten (carlfk) 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 #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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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