Bionic: OpenGL not properly working with Intel IGP

Bug #1753084 reported by roots
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa-utils (Ubuntu)
Invalid
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

I'm running Ubuntu 18.04 Bionic daily with proposed updates enabled. I am using gnome-flashback (gnome-panel) with Compiz. I first recognised that Compiz is giving very high CPU loads according to top. At the same time, intel_gpu_top shows GPU usage at an unchanged 0%. The same happens when running glmark2: CPU usage climbs to >400% while GPU stays at 0%. Interestingly, OpenGL seems to be enabled - please see the glxinfo outputs below. Switching to todays latest oibaf drivers did not make any difference.

Any pointers are much appreciated.

r.

---

H/W:

CPU: Core i7-7700k @ 5GHz
GPU: Using Intel IGP (HD630)
RAM: 16GB DDR4
SSD: Intel Optane

S/W:

$ cat /proc/version
Linux version 4.15.0-11-generic (buildd@lgw01-amd64-016) (gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)) #12-Ubuntu SMP Fri Feb 23 18:39:58 UTC 2018

$ lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04)
        Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
        Kernel driver in use: i915

$ modinfo i915
srcversion: 4963AD5BD78D754BBD09EAF
name: i915
vermagic: 4.15.0-11-generic SMP mod_unload
signat: PKCS#7

$ dpkg -l | grep xserver-xorg-video-intel
ii xserver-xorg-video-intel 2:2.99.917+git20171229-1 amd64
$ dpkg -l | grep xorg
ii xorg 1:7.7+19ubuntu5 amd64
$dpkg -l | grep mesa
ii libegl1-mesa:amd64 18.0.0~rc4-1ubuntu3

$ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.1.0-devel
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.1.0-devel
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.1.0-devel
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

$ glxinfo | grep -i direct
direct rendering: Yes
    GL_ARB_direct_state_access, GL_ARB_draw_buffers,
    GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts,
    GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect,

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1753084/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
roots (roots)
affects: ubuntu → xorg (Ubuntu)
roots (roots)
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
roots (roots) wrote :

Status changed to invalid, as I was obviously not using GPU rendering after applying some updates from Proposed. Did a clean 18.04 reinstall and problem does not occur anymore.

Changed in mesa-utils (Ubuntu):
status: New → Invalid
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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