[apport] vbetool crashed with SIGILL

[Baekeland]

Binary package hint: vbetool

Ubuntu Feisty 7x

ProblemType: Crash
Architecture: i386
Date: Sat Mar 24 13:31:32 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/vbetool
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: 4
SourcePackage: vbetool
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
 ?? ()
 ?? () from /lib/libx86.so.1
Uname: Linux baekeland-desktop 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux
UserGroups:

[Apport retracing service (apport)]

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

[Daniel Hahler (blueyed)]

Setting to confirmed after assigning 14 dupes.

[Aaron Waite (volvoguy)]

Lots of bug reports with this same title and symptoms, so hopefully I'm in the right place.

The error/bug report tool informs me that vbetool crashes whenever I wake from suspend. Sometimes I'm not able to wake at all and need to do a hard reset. That seems to be more frequent though when I actually tell it to sleep compared to just closing the lid of my laptop. This is a Toshiba Portege S100 - one of the Canonical-supplied laptops for the laptop testing team (more hardware info on that wiki page if it's needed). Let me know if you need any other logs or other information.

This was submitted via the GUI bug reporting tool, so I assume the data from that report made it's way in here somewhere.

Aaron

[Leon van der Ree (lvanderree)]

I have this same error when I resume from standby with my toshiba M200.

By the way, very cool sounds coming from my machine when entering and leaving standby, I like it (the beep)

[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.

[B&M (tryingubuntu)]

Since I am using Ubuntu 9.04 I don't seem to get this error any more.

Thanks

Dimitrios Symeonidis a écrit :
> 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
>
>

[Dimitrios Symeonidis (azimout)]

anyone else?

[kornykyano (kornykyano)]

I use ubuntu 8.04.2 and I do not have that problem.
Thank you

2009/4/19 Dimitrios Symeonidis <email address hidden>

> anyone else?
>
> --
> [apport] vbetool crashed with SIGILL
> https://bugs.launchpad.net/bugs/95559
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[dilasso (roland-dunzendorfer-at)]

I still use 8.04 and the problem still exists.

As I had the problem since updating from 7.04 I'm a bit affraid of updating
again to a newer version. Will have a try in a view days

roland

On Mon, Apr 20, 2009 at 4:01 AM, kornykyano <email address hidden> wrote:

> I use ubuntu 8.04.2 and I do not have that problem.
> Thank you
>
>
> 2009/4/19 Dimitrios Symeonidis <email address hidden>
>
> > anyone else?
> >
> > --
> > [apport] vbetool crashed with SIGILL
> > https://bugs.launchpad.net/bugs/95559
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> [apport] vbetool crashed with SIGILL
> https://bugs.launchpad.net/bugs/95559
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Dimitrios Symeonidis (azimout)]

two people have said this is fixed. marking as fix released.
if anyone still has this issue, please come forward. thank you