usplash crashed with signal 5 on reboot after feisti 7.04 update

Bug #88915 reported by Mark Gumprecht
196
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: usplash

After a feisti 7.04 update. The machine wouldn't boot to gdm. I have the nvidia driver version 1.0-9746 loaded. I had to reload the driver and the machine booted fine, that is when I received the crash report.

ProblemType: Crash
Architecture: i386
Date: Wed Feb 28 13:26:52 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /sbin/usplash
Package: usplash 0.4-43
ProcCmdline: /sbin/usplash -c -x 1024 -y 768
ProcCwd: /dev/.initramfs
ProcEnviron:
 LANGUAGE=
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: usplash
Stacktrace:
 #0 0xb7e11f6a in ?? () from /lib/libx86.so.1
 #1 0xb7e13800 in ?? () from /lib/libx86.so.1
 #2 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 13834):
 #0 0xb7e11f6a in ?? () from /lib/libx86.so.1
 #1 0xb7e13800 in ?? () from /lib/libx86.so.1
 #2 0x00000000 in ?? ()
Uname: Linux itmobile1 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
Mark Gumprecht (mgumprecht) wrote :
Revision history for this message
C de-Avillez (hggdh2) wrote :

Thank you for your bug report.

Unfortunately the stack trace / backtrace is not detailed enough to help. If this bug is reproducible at will, could you please:

1. add to your /etc/apt/sources.list the debug symbols repository? You can edit it directly with the editor of your preference (as root), and add at the bottom the following line:

deb http://people.ubuntu.com/~pitti/ddebs feisty main universe

You can also use Synaptic (under Gnome, go to System/Administration/Synaptic Package Manager and then, on Synaptic, select Settings/Repositories, and add the entry under the "Third Party" tab.

Please read on https://wiki.ubuntu.com/DebuggingProgramCrash?highlight=%28%2F%2Fpeople.ubuntu.com%2F%7Epitti%2Fddebs%29 for details.

2. update the repositories, but do not install any upgraded package.

3. Now we have two options: we can just retrace the report you have, or we can try to reproduce it. I think, right now, retracing is simpler.

Your issue report should be at /var/crash. Open a terminal session, and then:

cd /var/crash

Find the name of the bug report, and issue

apport-retrace <name of the bug report file> -o 88915.retrace

this command will take a bit to complete, and during its execution it will download any necessary debug packages.

After the completion of the retrace, please upload the newly-created report here.

Thank you.

Changed in usplash:
assignee: nobody → hggdh2
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) wrote :

Debug backtrace for the crash:

#0 0xb7e11f6a in run_vm86 () at lrmi.c:526
No locals.
#1 0xb7e1263b in LRMI_int (i=16, r=0xb7fc8cc0) at lrmi.c:844
        seg = 49152
        off = 3732
#2 0xb7f748fa in vesa_setmode (mode=3, prv_mode=0)
    at /build/buildd/usplash-0.4/svgalib/src/vesa.c:213
        i = <value optimized out>
        mode8 = 0
#3 0xb7f70021 in initialize ()
    at /build/buildd/usplash-0.4/svgalib/src/vga.c:2016
        i = <value optimized out>
        siga = {__sigaction_handler = {
    sa_handler = 0xb7f5dfa0 <_fini+1358060>,
    sa_sigaction = 0xb7f5dfa0 <_fini+1358060>}, sa_mask = {__val = {
      3086340048, 1, 3086962676, 3086850568, 3220145812, 3220145892,
      3086893315, 3086340048, 3220145872, 3086850128, 3086345478, 0,
      1550688371, 0, 1, 16777216, 2351837290, 0, 3086404714, 3086463969,
      3220145876, 3086327808, 149500, 3086464272, 3220145936, 3086850128,
      3086345469, 15697768, 1901610309, 0, 3086476708, 3220147344}},
  sa_flags = -1074819952, sa_restorer = 0xb7f6fd29 <initialize+9>}
#4 0xb7f705dc in vga_setmode (mode=12)
    at /build/buildd/usplash-0.4/svgalib/src/vga.c:2245
        modeinfo = <value optimized out>
#5 0xb7f64467 in usplash_svga_setmode () at usplash_svga.c:108
        mode = -1
        has_failed = 0
#6 0xb7f645e1 in usplash_svga_init () at usplash_svga.c:147
        rc = 0
        mode = -1074820136
#7 0xb7f62b91 in usplash_init () at libusplash.c:174
No locals.
#8 0xb7f6320b in usplash_setup (xres=1024, yres=768, v=0) at libusplash.c:339
        ret = 0
        ncolors = 0
        theme_handle = (void *) 0x804c030
        htheme = (struct usplash_theme *) 0xbfef884c
        maxarea = -1208052928
        ratio = 3084981284
#9 0x08048e10 in main (argc=6, argv=0xbfef8d14) at usplash.c:119
        i = 6
        ret = 0
        xres = 1024
        yres = 768
        verbose = 0
        t1 = {tv_sec = 0, tv_usec = 40000}
        t2 = {tv_sec = 0, tv_usec = 40000}
        iv = {it_interval = {tv_sec = 0, tv_usec = 40000}, it_value = {
    tv_sec = 0, tv_usec = 40000}}

Revision history for this message
C de-Avillez (hggdh2) wrote :

I am confirming this bug. We have some other bugs that are matching in the backtrace, and some others that are a probable match. I am duplicating them all against this bug.

Please undup any you think are not the same issue.

Changed in usplash:
assignee: hggdh2 → nobody
importance: Undecided → Medium
status: Needs Info → Confirmed
importance: Medium → Undecided
status: Confirmed → Rejected
importance: Undecided → Medium
status: Rejected → Confirmed
Revision history for this message
C de-Avillez (hggdh2) wrote :

I am also marking as duplicates 85742, 86459, 86551, 86728, 87047, and 87449. Although on a previous version (0.4-41), and without a usable backtrace, they all seem related (they may also have been solved by the fixes on 0.4-43, I do not know).

Revision history for this message
C de-Avillez (hggdh2) wrote :

Bug # 86666 may be related (but it is on AMD64 only, so far, and ends with a kernel hard crash).

Given the amount of dups, I am raising the importance here.

Changed in usplash:
importance: Medium → High
Revision history for this message
Jörgen Lidholm (jorgen-lidholm) wrote :

usplash is also crashing on boot for me. On an intel centrino duo.

Revision history for this message
miked (miked11) wrote :

root@Ubuntu704Beta:~# apt-get install usplash-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
usplash-dbgsym is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.

Revision history for this message
miked (miked11) wrote :

I have tried install the debugging symbols, but they don't really show up there in the report sent to the mysterious developers.

Revision history for this message
miked (miked11) wrote :

3. Now we have two options: we can just retrace the report you have, or we can try to reproduce it. I think, right now, retracing is simpler.

Your issue report should be at /var/crash. Open a terminal session, and then:

cd /var/crash

Find the name of the bug report, and issue

apport-retrace <name of the bug report file> -o 88915.retrace

this command will take a bit to complete, and during its execution it will download any necessary debug packages.

After the completion of the retrace, please upload the newly-created report here.

The name of my usplash crash file is:_sbin_usplash.0.crash

root@Ubuntu704Beta:~# apport-retrace _sbin_usplash.0.crash -o 88915.retrace
ERROR: "_sbin_usplash.0.crash" is neither an existing report file nor a Launchpad bug number
root@Ubuntu704Beta:~#

Revision history for this message
C de-Avillez (hggdh2) wrote :

@miked: the crash file name should be the last parameter on the call to apport-retrace:

cd /var/crash
apport-retrace -o 88915.retrace _sbin_usplash.0.crash

Revision history for this message
miked (miked11) wrote : Re: usplash crashed with signal segsiv

valgrind?

Revision history for this message
miked (miked11) wrote :

strace

Revision history for this message
miked (miked11) wrote :

Thanks about the re-trace thing, I think someone tried to tell me that at least once before but something else must of been wrong at the time.

root@Ubuntu704Beta:~# cd /var/crash
root@Ubuntu704Beta:/var/crash# apport-retrace -o 88915.retrace _sbin_usplash.0.crash
WARNING: package libsepol1-dbgsym not available
WARNING: package liblocale-gettext-perl-dbgsym not available
WARNING: package libncurses5-dbgsym not available
WARNING: package libtext-iconv-perl-dbgsym not available
WARNING: package libss2-dbgsym not available
WARNING: package busybox-initramfs-dbgsym not available
WARNING: package volumeid-dbgsym not available
WARNING: package libuuid1-dbgsym not available
WARNING: package libvolume-id0-dbgsym not available
WARNING: package grepmap-dbgsym not available
WARNING: package libklibc-dbgsym not available
WARNING: package klibc-utils-dbgsym not available
WARNING: package libusplash0-dbgsym not available
WARNING: package libtext-charwidth-perl-dbgsym not available
WARNING: package libc6-dbgsym not available
WARNING: package libcomerr2-dbgsym not available
WARNING: package e2fslibs-dbgsym not available
WARNING: package ncurses-bin-dbgsym not available
WARNING: package libselinux1-dbgsym not available
WARNING: package perl-base-dbgsym not available
WARNING: package libdevmapper1.02-dbgsym not available
WARNING: package libblkid1-dbgsym not available
WARNING: package module-init-tools-dbgsym not available
WARNING: package cpio-dbgsym not available
WARNING: package sed-dbgsym not available
WARNING: package belocs-locales-bin-dbgsym not available
WARNING: package libx86-1-dbgsym not available
WARNING: package procps-dbgsym not available
WARNING: package dmsetup-dbgsym not available
WARNING: package e2fsprogs-dbgsym not available
WARNING: package udev-dbgsym not available
WARNING: libx86-1-dbgsym is not available
WARNING: libusplash0-dbgsym is not available
WARNING: libc6-dbgsym is not available
WARNING: libc6-i686-dbgsym is not available
WARNING: usplash-theme-ubuntu-dbgsym is not available
WARNING: libc6-i686-dbgsym is not available
root@Ubuntu704Beta:/var/crash#

Revision history for this message
miked (miked11) wrote :
Download full text (8.0 KiB)

root@Ubuntu704Beta:~# cd/var/crash
bash: cd/var/crash: No such file or directory
root@Ubuntu704Beta:~# cd /var/crash
root@Ubuntu704Beta:/var/crash# apport-retrace -o 88915.retrace _sbin_usplash.0.crash
WARNING: package libsepol1-dbgsym not available
WARNING: package liblocale-gettext-perl-dbgsym not available
WARNING: package libncurses5-dbgsym not available
WARNING: package libtext-iconv-perl-dbgsym not available
WARNING: package libss2-dbgsym not available
WARNING: package busybox-initramfs-dbgsym not available
WARNING: volumeid-dbgsym version 103-0ubuntu14 required, but 093-0ubuntu18 is available
WARNING: package libuuid1-dbgsym not available
WARNING: package libvolume-id0-dbgsym not available
WARNING: package grepmap-dbgsym not available
WARNING: libklibc-dbgsym version 1.4.30-3ubuntu2 required, but 1.4.10-0ubuntu3 is available
WARNING: klibc-utils-dbgsym version 1.4.30-3ubuntu2 required, but 1.4.10-0ubuntu3 is available
WARNING: package libusplash0-dbgsym not available
WARNING: package libtext-charwidth-perl-dbgsym not available
WARNING: libc6-dbgsym version 2.5-0ubuntu12 required, but 2.4-1ubuntu12 is available
WARNING: package libcomerr2-dbgsym not available
WARNING: package e2fslibs-dbgsym not available
WARNING: package ncurses-bin-dbgsym not available
WARNING: package libselinux1-dbgsym not available
WARNING: package perl-base-dbgsym not available
WARNING: libdevmapper1.02-dbgsym version 2:1.02.08-1ubuntu5 required, but 2:1.02.07-1ubuntu2 is available
WARNING: package libblkid1-dbgsym not available
WARNING: package module-init-tools-dbgsym not available
WARNING: package cpio-dbgsym not available
WARNING: package sed-dbgsym not available
WARNING: belocs-locales-bin-dbgsym version 2.4-2ubuntu2 required, but 2.4-1ubuntu6 is available
WARNING: package libx86-1-dbgsym not available
WARNING: package procps-dbgsym not available
WARNING: dmsetup-dbgsym version 2:1.02.08-1ubuntu5 required, but 2:1.02.07-1ubuntu2 is available
WARNING: package e2fsprogs-dbgsym not available
WARNING: udev-dbgsym version 103-0ubuntu14 required, but 093-0ubuntu18 is available
Selecting previously deselected package belocs-locales-bin-dbgsym.
(Reading database ... 295770 files and directories currently installed.)
Unpacking belocs-locales-bin-dbgsym (from .../belocs-locales-bin-dbgsym_2.4-1ubuntu6_i386.ddeb) ...
Selecting previously deselected package dmsetup-dbgsym.
Unpacking dmsetup-dbgsym (from .../dmsetup-dbgsym_2%3a1.02.07-1ubuntu2_i386.ddeb) ...
Selecting previously deselected package klibc-utils-dbgsym.
Unpacking klibc-utils-dbgsym (from .../klibc-utils-dbgsym_1.4.10-0ubuntu3_i386.ddeb) ...
Selecting previously deselected package libc6-dbgsym.
Unpacking libc6-dbgsym (from .../libc6-dbgsym_2.4-1ubuntu12_i386.ddeb) ...
Selecting previously deselected package libdevmapper1.02-dbgsym.
Unpacking libdevmapper1.02-dbgsym (from .../libdevmapper1.02-dbgsym_2%3a1.02.07-1ubuntu2_i386.ddeb) ...
Selecting previously deselected package libklibc-dbgsym.
Unpacking libklibc-dbgsym (from .../libklibc-dbgsym_1.4.10-0ubuntu3_i386.ddeb) ...
Selecting previously deselected package udev-dbgsym.
Unpacking udev-dbgsym (from .../udev-dbgsym_093-0ubuntu18_i386.ddeb) ...
Selecting pre...

Read more...

Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote : Re: usplash crashed with signal sigsiv
Revision history for this message
miked (miked11) wrote :

I have moved to Gusty Gibbons Final 7.10 via fresh install from Live CD.
So I guess you can close the bug as it relates to me, for now, and I will file if it happens again.
thanks

Revision history for this message
Martin Pitt (pitti) wrote :

Miked, thanks for reporting back. Since this did not get duplicates recently and it seems to be fixed at least for you, I close this. If anyone still experiences this on 7.10 (Gutsy), please yell and I'll reopen this. Thank you!

Changed in usplash:
status: Confirmed → 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.