Ubuntu
vbetool package

[apport] vbetool crashed with SIGSEGV in rdw()

Bug #90406 reported by salmon
52
Affects Status Importance Assigned to Milestone
vbetool (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: vbetool

Almost clean install of Feisty Herd 5 with nvidia drivers on Dell Latitude d820. Problem was reported after resuming from a suspend.

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 7 16:37:44 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/vbetool
Package: vbetool 1.0-0ubuntu1
PackageArchitecture: amd64
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: 11
SourcePackage: vbetool
StacktraceTop:
 rdw () from /lib/libx86.so.1
 fetch_data_word () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 X86EMU_exec () from /lib/libx86.so.1
 real_call () from /lib/libx86.so.1
Uname: Linux kyoto 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux
UserGroups:

Revision history for this message
salmon (rydland) wrote :
Revision history for this message
Chris Halse Rogers (raof) wrote :

I confirm this on my ASUS F3Jm laptop. Also on resume from suspend.

I've marked my bug as a duplicate of this one. I have some dbgsym packages installed, so the backtrace may be more helpful.

Changed in vbetool:
status: Unconfirmed → Confirmed
Sebastien Bacher (seb128)
Changed in vbetool:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:fetch_data_word (offset=65449) at x86emu/decode.c:328
x86emuOp_opcFF_word_RM (op1=<value optimized out>) at x86emu/ops.c:11259
X86EMU_exec () at x86emu/decode.c:124
real_call (registers=0x7fff1027c5a0) at thunk.c:215

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

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.

Changed in vbetool (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Monkey (monkey-libre) wrote :

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!

Changed in vbetool (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.