vbetool crashed with signal 5

Bug #132494 reported by TorenC
This bug report is a duplicate of:  Bug #95559: [apport] vbetool crashed with SIGILL. Edit Remove
6
Affects Status Importance Assigned to Milestone
vbetool (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: vbetool

I got a crash report on resuming from stand by on my Dell D820. I'm running the latest gutsy (as of yesterday, at least). Also, my caps lock and scroll lock lights are constantly blinking after this happens.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Aug 14 09:30:36 2007
Dependencies:
 libgcc1 1:4.2.1-3ubuntu1
 libx86-1 0.99-1.2ubuntu1
 gcc-4.2-base 4.2.1-3ubuntu1
 zlib1g 1:1.2.3.3.dfsg-5ubuntu2
 libc6 2.6.1-0ubuntu1
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/sbin/vbetool
NonfreeKernelModules: nvidia
Package: vbetool 1.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: vbetool post
ProcCwd: /usr/lib/hal/scripts
ProcEnviron: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin:/usr/bin/X11
Signal: 5
SourcePackage: vbetool
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
 ?? ()
 ?? () from /lib/libx86.so.1
Title: vbetool crashed with signal 5
Uname: Linux cs80719 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
TorenC (torenc) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:run_vm86 () at lrmi.c:526
LRMI_call (r=0xbfaf7510) at lrmi.c:797
do_real_post (pci_device=256) at vbetool.c:201
do_post () at vbetool.c:225
main (argc=65535, argv=0xbfaf7644) at vbetool.c:115

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in vbetool:
importance: Undecided → Medium
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.