Mesa 9.0 (quantal) uses LLVMpipe (slow) on ThinkPad L412. Mesa 9.1 solves it.

Bug #1074824 reported by jmalter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Expired
Low
Unassigned

Bug Description

#803943 is marked as fixed, but it is not fixed.
With 12.10 and Intel HD Graphics the problem still persists

In idle phase compiz top show 80%-120% cpu and shows load between 1,2 and 2,2

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz 1:0.9.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,imgpng,grid,place,move,resize,vpswitch,mousepoll,animation,unitymtgrabhandles,gnomecompat,snap,session,workarounds,wall,expo,fade,ezoom,scale,unityshell]
CompositorRunning: compiz
Date: Sun Nov 4 09:34:10 2012
DistUpgraded: 2012-10-18 21:41:59,032 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.2.4: added
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:215a]
InstallationDate: Installed on 2012-04-27 (190 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: LENOVO 44036KG
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=5b92ef9d-8635-498c-b57d-ddf886a440ae ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: Upgraded to quantal on 2012-10-18 (16 days ago)
dmi.bios.date: 03/28/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET61WW (1.37 )
dmi.board.name: 44036KG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr81ET61WW(1.37):bd03/28/2012:svnLENOVO:pn44036KG:pvrThinkPadL412:rvnLENOVO:rn44036KG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 44036KG
dmi.product.version: ThinkPad L412
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.8.4-0ubuntu3
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
jmalter (joerg4711) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please do these:

Determine if the problem is Compiz or Unity (which runs inside compiz). You can do this by logging in to Gnome Classic (install gnome-session-fallback) and see if the problem persists. Alternatively, open some terminal windows, one running top, and in the other run ccsm, click on the Unity plugin and untick it to disable it temporarily. Does the CPU go down when just unity is removed? Remember to tick it again to enable Unity before logging in again.

Secondly, please collect stack information:
1. Copy the attached script to your home directory
2. Open a terminal (Ctrl+Alt+T)
3. Run: sudo sh ./dstack compiz >> compizcpu.txt
4. Repeat #3 many times.
5. Attach "compizcpu.txt" to this bug.

Changed in compiz (Ubuntu):
status: New → Incomplete
Revision history for this message
jmalter (joerg4711) wrote :

Hi Daniel,

thank you for your answer.

I installed gnome-session-fallback, and yes there is a difference.

With Unity top shows about 80%-120% CPU and the Load Index between 0,8 and 1,8.

The i switched from Unity to Gnome Classic with effects (not Gnome Classic 2D).
Top shows between 8% and 15% CPU and a Load Index between 0,1 and 0,3.

This night i will start your dstack Script every 10 second for a minimum of 8 hours and leave the laptop untouched.
Hope, thats ok for you.

Best regards
Joerg

Revision history for this message
Omer Akram (om26er) wrote :

One thing is clear in the logs that you do not have the necessary hardware acceleration to run Unity so its LLVMpipe related.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's surprising. It looks like a new-ish machine.

jmalter - Please run this command (from Gnome Classic) to confirm:
     /usr/lib/nux/unity_support_test -p
What does it show?

Revision history for this message
jmalter (joerg4711) wrote :

It shows:

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x301)
OpenGL version string: 2.1 Mesa 9.0

Not software rendered: no
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: no

Revision history for this message
jmalter (joerg4711) wrote :

Attached you will find the requested file

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks, that just confirms this is a duplicate of bug 1055936.

Revision history for this message
jmalter (joerg4711) wrote :

@Daniel

I solved my problem right now.

/usr/lib/nux/unity_support_test -p

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 9.1-devel

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

What i have done is:

apt-add-repository ppa:xorg-edgers/ppa
apt-get update
apt-get upgrade

This will install the newest Intel Driver. As you can see 3D Support is now active.

Revision history for this message
jmalter (joerg4711) wrote :

Top shows now for compiz about 2% cpu usage

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Mesa 9.0 (quantal) fails unity_support_test on ThinkPad L412. Mesa 9.1 works.

OK, so in summary:

Mesa 9.0 in quantal reports:
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x301)
OpenGL version string: 2.1 Mesa 9.0
which makes Unity slow (bug 1055936).

However Mesa 9.1 reports:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 9.1-devel
and everything works nicely.

affects: compiz (Ubuntu) → mesa (Ubuntu)
summary: - compiz consuming cpu when idle
+ Mesa 9.0 (quantal) fails unity_support_test on ThinkPad L412. Mesa 9.1
+ works.
Changed in mesa (Ubuntu):
status: Incomplete → New
affects: mesa (Ubuntu) → nux (Ubuntu)
affects: nux (Ubuntu) → mesa (Ubuntu)
summary: - Mesa 9.0 (quantal) fails unity_support_test on ThinkPad L412. Mesa 9.1
- works.
+ Mesa 9.0 (quantal) uses LLVMpipe (slow) on ThinkPad L412. Mesa 9.1
+ solves it.
Revision history for this message
penalvch (penalvch) wrote :

jmalter, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL as of May 16, 2014.

Is this reproducible in a supported release?

tags: added: bios-outdated-1.39
Changed in mesa (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mesa (Ubuntu) because there has been no activity for 60 days.]

Changed in mesa (Ubuntu):
status: Incomplete → Expired
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.