plymouthd crashed with SIGSEGV in ply_list_get_first_node()

Bug #554510 reported by Harri Paaso-Rantala
590
This bug affects 131 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: plymouth

?

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 3 12:29:12 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: ASUSTeK Computer INC. 901
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=5501056f-bbe0-456d-aa1e-b845f0065812 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0x17ca17 <ply_list_get_first_node+7>: mov (%eax),%eax
 PC (0x0017ca17) ok
 source "(%eax)" (0x4021bd44) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_list_get_first_node () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_list_get_first_node()
UserGroups:

dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Harri Paaso-Rantala (hapapr) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ply_list_get_first_node (list=0x98540a8) at ply-list.c:257
 ply_event_loop_run (loop=0x9859ab0) at ply-event-loop.c:1312
 main (argc=3, argv=0xbfc6e984) at main.c:1916

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: bugpattern-needed
Daniel Hahler (blueyed)
visibility: private → public
Changed in plymouth (Ubuntu):
status: New → Triaged
Revision history for this message
John D Wilson (john-wilsonet) wrote :

My machine is a Dell Inspiron 6000, Centrino proccessor. The bug occurs immediately after I log in.

Revision history for this message
ealthuis (ealthuis) wrote :

This may have nothing to do with the crash, however this is the sequence of events

Started Natty from hibernation (which usually works quite well) Had to power the system down and restart from sctatch. Sysyem came up fine, but failed when I started Firefox.

Crash message followed and Firefox continued.

Revision history for this message
Tommy Trussell (tommy-trussell) wrote :

My machine is an Acer Aspire 5100-3949 and is, unfortunately, a "bug magnet" with recent versions of ubuntu (poorly supported ATI Radeon Xpress graphics card, especially). This crash has been occurring on cold boot after a fresh reinstall using yesterday's daily build iso.

Revision history for this message
Observer (dbvweb) wrote :

@Tommy, you may want to try the boot flags "acpi=off noacpi nolapic" and see if it helps.

Revision history for this message
Chenheting (chenheting) wrote :

After I restart the machine, I got this bug.

Revision history for this message
Brian Murray (brian-murray) wrote :

Bug 743730 looks similar to this one.

tags: added: bugpattern-written
removed: bugpattern-needed
Revision history for this message
kaotik (lynxly-vk) wrote :

12.04 dev
ac100
similar bug

Revision history for this message
kjeld Olsen (kjeldo) wrote :

Same here, 12.04 AC100-10D PDN01E-00801EN5 32GB SD-card.

Revision history for this message
Steve Langasek (vorlon) wrote :

We believe this has been resolved with the application of a workaround for bug #553745. If you continue to see this behavior in Ubuntu 12.04 LTS, please reopen this report and provide details.

Changed in plymouth (Ubuntu):
status: Triaged → Fix Released
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.