usplash crash after reboot

Bug #407193 reported by Adon Metcalfe
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: usplash

[ 3.072520] usplash[917]: segfault at b7f8d530 ip 001d14f0 sp bffd6590 error 6 in libusplash.so.0[1ad000+2c000]

ProblemType: Crash
Architecture: i386
Date: Fri Jul 31 09:30:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/usplash
MachineType: Dell Inc. Latitude 2100
Package: usplash 0.5.32
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=46e81527-a661-4684-8855-17cb338ce66d ro quiet splash
ProcCmdline: /sbin/usplash -c
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0xe724f0 <memset_var+1072>: mov %edi,(%eax)
 PC (0x00e724f0) ok
 source "%edi" ok
 destination "(%eax)" (0xb8087530) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: usplash
StacktraceTop:
 memset_var () from /lib/libusplash.so.0
 bogl_tcfb_clear () from /lib/libusplash.so.0
 usplash_bogl_clear () from /lib/libusplash.so.0
 usplash_clear () from /lib/libusplash.so.0
 clear_text () from /lib/libusplash.so.0
Tags: ubuntu-unr
Title: usplash crashed with SIGSEGV in memset_var()
Uname: Linux 2.6.31-4-generic i686
UserGroups:

UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1024
 yres=576
dmi.bios.date: 04/08/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0W785N
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/08/2009:svnDellInc.:pnLatitude2100:pvr:rvnDellInc.:rn0W785N:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude 2100
dmi.sys.vendor: Dell Inc.

Revision history for this message
Adon Metcalfe (adon-metcalfe-gmail) wrote :
visibility: private → public
tags: removed: need-i386-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.