(Intel KMS) usplash crashed with SIGSEGV in memset_var()

Bug #406569 reported by Robert Hooker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: usplash

Usplash has never worked under KMS (I've been using it since january) when i915 is built into the kernel or loaded early from an initrd. It loads, displays the initial graphic then segfaults and further usplash events don't happen which is a problem when someone is using usplash and needs enter their crypt password. Perhaps splash should be disabled for intel cards for karmic since KMS is on by default? Or i915 could be removed from the initrd by the cryptsetup package? If there is any more info I can provide that would help, please let me know.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jul 29 13:45:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/usplash
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway AOA150
Package: usplash 0.5.32
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=0810fa94-6177-41ba-b640-9e35b5bac68f ro quiet splash enable_mtrr_cleanup mtrr_spare_reg_nr=1 pcie_aspm=force
ProcCmdline: /sbin/usplash -c
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0xb7f214f0 <memset_var+1072>: mov %edi,(%eax)
 PC (0xb7f214f0) ok
 source "%edi" ok
 destination "(%eax)" (0xb7d15530) in non-writable VMA region: 0xb7d15000-0xb7d17000 r-xp /usr/lib/usplash/usplash-theme-ubuntu.so
SegvReason: writing VMA /usr/lib/usplash/usplash-theme-ubuntu.so
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=600
dmi.bios.date: 12/09/2008
dmi.bios.vendor: Gateway
dmi.bios.version: v0.3103
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Gateway
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGateway:bvrv0.3103:bd12/09/2008:svnGateway:pnAOA150:pvrLU.S050B.111:rvnGateway:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA150
dmi.product.version: LU.S050B.111
dmi.sys.vendor: Gateway

Revision history for this message
Robert Hooker (sarvatt) wrote :
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Robert Hooker (sarvatt) wrote :

(gdb) backtrace
#0 memset_var (d=0xb7fe1000, c=256, offset=332, len=360, b=32) at bogl-cfb.c:108
#1 0x008897d6 in bogl_tcfb_clear (x1=332, y1=603, x2=<value optimized out>, y2=607, c=0) at bogl-tcfb.c:143
#2 0x00873e17 in usplash_bogl_clear (x1=332, y1=457, x2=692, y2=607, colour=0) at usplash_bogl.c:82
#3 0x00871096 in usplash_clear (x1=332, y1=457, x2=692, y2=607, colour=0) at libusplash.c:228
#4 0x00872396 in clear_text () at libusplash.c:667
#5 0x08049162 in main (argc=1, argv=0xbffff844) at usplash.c:135

bt full attached with more info

Revision history for this message
Robert Hooker (sarvatt) wrote :

I recompiled it with more debug info and enabled some printf's around where it was crashing incase it helps -- backtrace attached

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.