video related gnome-shell crash on fedora 19

Discussions about using Linux guests in VirtualBox.
Post Reply
tsteven4
Posts: 14
Joined: 27. Sep 2013, 02:19

video related gnome-shell crash on fedora 19

Post by tsteven4 »

I am running box 4.2.18 on a windows 7 host with a fedora 19 guest. Things go ok with my guest until I install guest additions. After rebooting gnome-shell coredumps and abrt thinks about it at 100% cpu for about 30 minutes. This is with no 2d or 3d acceleration enabled for the guest. There are clues in /var/log/messages (messages.txt attached) and /var/log/Xorg.0.log (attached). In messages.txt I see:

Sep 26 18:05:40 jenny /usr/bin/dbus-launch[819]: OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.
Sep 26 18:05:40 jenny /usr/bin/dbus-launch[819]: libGL error: failed to load driver: vboxvideo
Sep 26 18:05:40 jenny /usr/bin/dbus-launch[819]: libGL error: Try again with LIBGL_DEBUG=verbose for more details.

I also see these messages in Xorg.0.log:

[ 40.413] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 40.414] (EE) AIGLX: reverting to software rendering

which suggests to me I enable 3d acceleration. However, when I shut the guest down, enable 3d acceleration, and start the guest the guest is unstable and crashes within a few minutes. I would not consider causing abrt to spend 30 minutes analyzing the failure a graceful failure mode. However, the failure mode with 3d acceleration enabled is much more serious, it is difficult to keep the guest running long enough to uninstall guest additions. But if you can manage to do this then the guest works again, albeit w/o the features provided by guest additions.

The abrt behavior is triggered by a core dump of gnome-shell that was killed due to a segmentation fault. I can provide the coredump or the analysis done by abrt if it would be useful.

Any help would be appreciated.
Attachments
Xorg.0.log
Xorg.0.log from boot with 3d disabled
(28.11 KiB) Downloaded 10 times
messages.txt
3d disabled, messages
(91.91 KiB) Downloaded 5 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: video related gnome-shell crash on fedora 19

Post by Perryg »

Enable 3D in the guest settings and start the guest. Once the guest has started and crashed post the guests log file (as an attachment)
tsteven4
Posts: 14
Joined: 27. Sep 2013, 02:19

Re: video related gnome-shell crash on fedora 19

Post by tsteven4 »

Here is the guest log after a crash with 3d enabled and guest additions installed.
Attachments
Fedora19-2013-09-27-17-08-44.log
guest log after crash with 3d enabled
(76.18 KiB) Downloaded 26 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: video related gnome-shell crash on fedora 19

Post by Perryg »

I see your guest is having issues with your Intel Graphics adapter.
Does the adapter have a fallback to low graphics to save energy?
I would make sure that you have the newest drivers for you GPU.

Also post the results of the following from the guests terminal

Code: Select all

glxinfo | grep OpenGL
Note: you may need to install mesa-utils to use glxinfo.
tsteven4
Posts: 14
Joined: 27. Sep 2013, 02:19

Re: video related gnome-shell crash on fedora 19

Post by tsteven4 »

Here is the glxinfo output:

[tsteven4@jenny ~]$ glxinfo | grep OpenGL
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
OpenGL vendor string: Humper
OpenGL renderer string: Chromium
OpenGL version string: 2.1 Chromium 1.9
OpenGL shading language version string: 1.20 - Intel Build 8.15.10.2202
OpenGL extensions:
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: video related gnome-shell crash on fedora 19

Post by Perryg »

That looks fine. Don't forget to answer the other questions.
tsteven4
Posts: 14
Joined: 27. Sep 2013, 02:19

Re: video related gnome-shell crash on fedora 19

Post by tsteven4 »

Perry,

I don't know about the energy mode yet, but I did update the driver to 8.15.10.2993. The guest still crashes.

Thanks
tsteven4
Posts: 14
Joined: 27. Sep 2013, 02:19

Re: video related gnome-shell crash on fedora 19

Post by tsteven4 »

I changed the power mode from balanced to maximum performance. The guest still crashes.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: video related gnome-shell crash on fedora 19

Post by Perryg »

I would then post a ticket to bugtracker. The Intel Graphics has been a problem for some time but it seems to be getting better. Be sure to post the guests log file and as much information as you can. Also posting the ticket number here so others can track this would be advised.
Post Reply