Ticket #4558 (closed defect: wontfix)

Opened 12 years ago

Last modified 11 years ago


Reported by: AdamK Owned by:
Component: other Version: VirtualBox 3.0.2
Keywords: Cc:
Guest type: other Host type: other


Change History

comment:1 Changed 12 years ago by AdamK

Loading Virtualbox module, on X display without OpenGL (NX server in my case) fails with following dmesg output:

[21784.572037] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [21788.234036] <6>VBoxTestOGL[9517]: segfault at 0 ip 00b0eda8 sp bf927d90 error 4 in[aa6000+80000] [21946.159690] vboxdrv: Trying to deactivate the NMI watchdog permanently... [21946.159695] vboxdrv: NMI watchdog either active or at least initialized. Please disable the NMI [21946.159697] vboxdrv: watchdog by specifying 'nmi_watchdog=0' at kernel command line.

If display has Xserver, loading works.

comment:2 Changed 12 years ago by AdamK

To add: after loading module in OpenGL-able display, virtual machine works in non-opengl display.

comment:3 Changed 12 years ago by frank

So VBoxTestOGL segfaults for some reason. Could you provide a  core dump? Just run this application manually and attach the compressed core dump to this defect or send it to frank _dot_ mehnert _at_ sun _dot_ com.

Don't forget to specify the VBox package you installed on your host (exact package name please).

comment:4 Changed 12 years ago by AdamK

I was able to repeat reperoduce it today:

I'm using: virtualbox-3.0 3.0.2-49928_Ubuntu_intrepid

from following repository: intrepid non-free

I sent coredump to the provided email address (I couldn't attach it here - to big even when compressed)

comment:5 Changed 12 years ago by frank

  • Status changed from new to closed
  • Resolution set to wontfix

I will close this bug. The reason is that crashes in VBoxTestOGL are sometimes expected. We've seen crashes there as well. In that case the application crashes in some OpenGL driver. One example are the Mesa drivers of Debian/unstable which sometimes crash in the Radeonm code but after some investigation we found out that this crash is actually a bug in Mesa not in our code. The purpose of the dedicated VBoxTestOGL application is to not crash the whole application when doing feature checks for OpenGL. VBoxTestOGL as contained in the next release will not generate core dumps nor any strange message anymore.

comment:6 Changed 11 years ago by Shinkan

Still crashing with Oracle VM VirtualBox 3.2 on Windows 7

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use