vbetool crashed with SIGILL

[vlowther]

Binary package hint: vbetool

vbetool crashed on resume after latest updates to Hardy.

ProblemType: Crash
Architecture: i386
Date: Thu Jan 3 20:37:53 2008
Dependencies:
 libgcc1 1:4.2.2-4ubuntu3
 libx86-1 0.99-1.2ubuntu2
 gcc-4.2-base 4.2.2-4ubuntu3
 zlib1g 1:1.2.3.3.dfsg-7ubuntu1
 libc6 2.7-5ubuntu2
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/vbetool
NonfreeKernelModules: nvidia
Package: vbetool 1.0-1.1
PackageArchitecture: i386
ProcCmdline: /usr/sbin/vbetool vbestate restore
ProcCwd: /usr/lib/hal/scripts
ProcEnviron:
 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/lib/pm-utils/bin
 LC_COLLATE=C
Signal: 4
SourcePackage: vbetool
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/libx86.so.1
Title: vbetool crashed with SIGILL
Uname: Linux sentry-no 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:run_vm86 () at lrmi.c:526
LRMI_int (i=16, r=0xbfedebbc) at lrmi.c:844
do_vbe_service (AX=3, BX=0, regs=0xbfedebbc) at vbetool.c:158
do_set_mode (mode=3324, vga=1) at vbetool.c:373
restore_state_from (data=0x2010 " ") at vbetool.c:239

[vlowther (victor-lowther)]

after a bit more research, this happens only when the nvidia binary driver is loaded. We should just let the nvidia kernel driver take care of things when it is present. This bug should be moved to HAL and/or the pacjage that contains pm-suspend.

[Dimitrios Symeonidis (azimout)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Monkey (monkey-libre)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!