Hello! I run ubuntu 11.04 64bit with 2.6.39-3-generic kernel and I get latest xorg drivers from xorg-edgers ppa. I've got a vaio laptop with hybrid intel + ati graphics. I use the intel one, and keep the ati powered off with vgaswitcheroo. Everything was very good till yesterday. After today's upgrade of xserver-xorg-video-intel, I found a huge performance regression, making my system completely unusable. Performance got back to usual after downgrading to previous version that was on the ppa till yestarday. last stable version for me was: xserver-xorg-video-intel_2%3a2.15.0+git20110624.471115a9-0ubuntu0sarvatt~natty_amd64.deb unusable version is: xserver-xorg-video-intel_2%3a2.15.0+git20110627.44cd6ebf-0ubuntu0sarvatt~natty_amd64.deb (according to ppa mantainers the 44cd6ebf part in the name of the package should be the git commint identifier) just tell me more information is needed, I'm new here and I don't really now what informations are needed. I put some that comes to mi mind clem@vaio:~$ lspci -vnn | grep -i vga 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc NI Seymour [AMD Radeon HD 6470M] [1002:6760] (rev ff) (prog-if ff) clem@vaio:~$ dpkg -l | grep xorg ii libva1 1.0.12-1~xorgedgers Video Acceleration (VA) API for Linux -- runtime ii python-xkit 0.4.2.2 library for the manipulation of the xorg.conf ii xorg 1:7.6+4ubuntu3.1 X.Org X Window System ii xorg-docs-core 1:1.5.99.901-1ubuntu1 Core documentation for the X.org X Window System ii xserver-xorg 1:7.6+4ubuntu3.1 the X.Org X server ii xserver-xorg-core 2:1.10.2+git20110616+server-1.10-branch.9551f504-0ubuntu0sarvatt~natty Xorg X server - core server ii xserver-xorg-input-all 1:7.6+4ubuntu3.1 the X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev 1:2.6.0+git20110408.68a6a18f-0ubuntu0sarvatt X.Org X server -- evdev input driver ii xserver-xorg-input-mouse 1:1.7.0+git20110624.17806678-0ubuntu0sarvatt~natty X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.3.99+git20110116.0e27ce3a-0ubuntu12.1 Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-vmmouse 1:12.7.0+git20110624.fd140bfb-0ubuntu0sarvatt~natty X.Org X server -- VMMouse input driver to use with VMWare ii xserver-xorg-input-wacom 1:0.10.11-0ubuntu4 X.Org X server -- Wacom input driver ii xserver-xorg-video-apm 1:1.2.3+git20110526.6f8a776f-0ubuntu0sarvatt~natty X.Org X server -- APM display driver ii xserver-xorg-video-ark 1:0.7.3+git20110526.9d3769be-0ubuntu0sarvatt~natty X.Org X server -- ark display driver ii xserver-xorg-video-ati 1:6.14.99+git20110623.9bb31158-0ubuntu0sarvatt~natty X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-chips 1:1.2.4+git20110526.e4bd8648-0ubuntu0sarvatt~natty X.Org X server -- Chips display driver ii xserver-xorg-video-cirrus 1:1.3.2+git20110526.e4f80ffd-0ubuntu0sarvatt~natty X.Org X server -- Cirrus display driver ii xserver-xorg-video-fbdev 1:0.4.2+git20110526.a8721393-0ubuntu0sarvatt~natty X.Org X server -- fbdev display driver ii xserver-xorg-video-i128 1:1.3.4+git20110526.b9e0edbd-0ubuntu0sarvatt~natty X.Org X server -- i128 display driver hi xserver-xorg-video-intel 2:2.15.0+git20110624.471115a9-0ubuntu0sarvatt~natty X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-mach64 6.9.0+git20110526.ef55d1f1-0ubuntu0sarvatt~natty X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-mga 1:1.4.13.dfsg-3ubuntu0sarvatt X.Org X server -- MGA display driver ii xserver-xorg-video-neomagic 1:1.2.5+git20110526.a9d69f6d-0ubuntu0sarvatt~natty X.Org X server -- Neomagic display driver ii xserver-xorg-video-nouveau 1:0.0.16+git20110623.ab89aa02-0ubuntu0sarvatt~natty X.Org X server -- Nouveau display driver (experimental) ii xserver-xorg-video-openchrome 1:0.2.904+svn916-1ubuntu0sarvatt X.Org X server -- VIA display driver ii xserver-xorg-video-qxl 0.0.12-1ubuntu4 X.Org X server -- QXL display driver ii xserver-xorg-video-r128 6.8.1+git20110526.3de85360-0ubuntu0sarvatt~natty X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon 1:6.14.99+git20110623.9bb31158-0ubuntu0sarvatt~natty X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-rendition 1:4.2.4+git20110526.541d1193-0ubuntu0sarvatt~natty X.Org X server -- Rendition display driver ii xserver-xorg-video-s3 1:0.6.3+git20110526.381ace93-0ubuntu0sarvatt~natty X.Org X server -- legacy S3 display driver ii xserver-xorg-video-s3virge 1:1.10.4+git20110526.a568407e-0ubuntu0sarvatt~natty X.Org X server -- S3 ViRGE display driver ii xserver-xorg-video-savage 1:2.3.2+git20110526.d177ae0b-0ubuntu0sarvatt~natty X.Org X server -- Savage display driver ii xserver-xorg-video-siliconmotion 1:1.7.5+git20110526.087226bf-0ubuntu0sarvatt~natty X.Org X server -- SiliconMotion display driver ii xserver-xorg-video-sis 1:0.10.3+git20110608.94f23a56-0ubuntu0sarvatt~natty X.Org X server -- SiS display driver ii xserver-xorg-video-sisusb 1:0.9.4+git20110608.241dd519-0ubuntu0sarvatt~natty X.Org X server -- SiS USB display driver ii xserver-xorg-video-tdfx 1:1.4.3+git20110526.0c4ffbec-0ubuntu0sarvatt~natty X.Org X server -- tdfx display driver ii xserver-xorg-video-trident 1:1.3.4+git20110526.de79bbea-0ubuntu0sarvatt~natty X.Org X server -- Trident display driver ii xserver-xorg-video-tseng 1:1.2.4+git20110613.542e65de-0ubuntu0sarvatt~natty X.Org X server -- Tseng display driver ii xserver-xorg-video-vesa 1:2.3.0+git20110526.0b02c685-0ubuntu0sarvatt~natty X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:11.0.3+git20110526.0142bb8d-0ubuntu0sarvatt~natty X.Org X server -- VMware display driver ii xserver-xorg-video-voodoo 1:1.2.4+git20110526.614ccdf6-0ubuntu0sarvatt~natty X.Org X server -- Voodoo display driver
The important bit of information that you need to tell me that Bryce hinted at, was what exactly slowed down? What desktop environment and applications are you running? Do you have a precise benchmark that hints as to the nature of the slowdown? Can you please attach both Xorg.log and dmesg?
Created attachment 48484 [details] Xorg.0.log with new driver git20110627.44cd6ebf
Created attachment 48485 [details] dmesg with new driver git20110627.44cd6ebf
(In reply to comment #1) > The important bit of information that you need to tell me that Bryce hinted at, > was what exactly slowed down? What desktop environment and applications are you > running? Do you have a precise benchmark that hints as to the nature of the > slowdown? > > Can you please attach both Xorg.log and dmesg? Files attached. I'm using ubuntu unity, and the whole desktop is quite unusable with new driver. everything is slowed down. if i open a terminal and i type something, the character I've typed are displayed with a delay of several seconds. The same happens if I open a browser and I type a address. If a move a window with the mouse, the windows stays in the original position. only after several seconds it is suddenly redrawn in the new position. if the unity launcher is hidden and i put the mouse on the corner, it takes very long to appear again. after few time, if i have several applications opened, the desktop becomes completely unusable. I have to open a vt by pressing Ctrl+Alt+F1 and reboot. Maybe it's not a bug in the driver, there is only some problems with my installation. I don't know... but every problems disappears if a go back to the previous version of the driver (git20110624.471115a9) and the system is very stable and smooth. (maybe the new driver brings some new feature that is not fully supported by my hardware?)
Two more things: can you give me a dmesg after using the system for a while, and can you try a 3.0.0 kernel (probably need a mainline ppa)?
(In reply to comment #5) > Two more things: can you give me a dmesg after using the system for a while, > and can you try a 3.0.0 kernel (probably need a mainline ppa)? The files that i attached before are taken after some minutes of usage. Do you want me to get others after some more time? or just after the login? Tomorrow I will give a try to kernel v3.0-rc4 and report back
(In reply to comment #6) > The files that i attached before are taken after some minutes of usage. Do you > want me to get others after some more time? or just after the login? No, that's fine. I just wanted to be sure that you had observed the failure before you grabbed the dmesg so I could be certain if one of the expected failure modes was being reported. It wasn't, but I know of many more bugs... > Tomorrow I will give a try to kernel v3.0-rc4 and report back Thanks.
I'm using right now the lastest kernel that i found in deb format, it's 3.0rc4 and the problem seems solved. the system is smooth and responsive once again. During normal use i cannot see any difference between the two versions of the intel driver. If it's useful to have a more accurate measurement of the performance of the two drivers, somebody should suggest me a proper benchmark tool because i don't know any.
(In reply to comment #8) > I'm using right now the lastest kernel that i found in deb format, it's 3.0rc4 > and the problem seems solved. the system is smooth and responsive once again. > During normal use i cannot see any difference between the two versions of the > intel driver. No, you wont really be able to tell since using a compositing WM drops the performance immensely, and then sna is only about 50% faster -- the difference between fast and very fast, until you hit one of the boundary cases handled by sna but forces a software fallback on uxa. And even if you aren't both uxa and sna on SNB are GPU bound (more or less), just sna uses about 1/5 the CPU to do so. (Conversely if you were just to measure how fast both paths could feed the GPU, i.e. without caring for latency of rendering, sna is 5x faster.) > If it's useful to have a more accurate measurement of the performance of the > two drivers, somebody should suggest me a proper benchmark tool because i don't > know any. That's fine. I just needed to characterise your problem, as it turns out the issue was a rather more severe and fundamental bug than just merely bad performance.
Bisection suggests the fix is in this range, all of which are unbootable: commit 9e3c256d7d56a12a3242222945ce8e6347f93fa0 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed May 18 13:51:43 2011 -0700 drm/i915: initialize gen6 rps work queue on Sandy Bridge and Ivy Bridge commit 56184e3da005e0259fc628706351b54fcc4527db Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue May 17 14:03:50 2011 +0100 drm/i915/sdvo: Reorder i2c initialisation before ddc proxy commit 61e499bf05254aca0fab08e2c91643331a15e725 Author: Keith Packard <keithp@keithp.com> Date: Tue May 17 16:13:52 2011 -0700 drm/i915: FDI link training broken on Ironlake by Ivybridge integration commit a51f7a66fb5e4af5ec4286baef940d06594b59d2 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Thu May 5 14:42:26 2011 -0700 drm/i915: enable rc6 by default commit c1a9f047638b27e481d097910604316b8a0d132b Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Thu May 5 15:24:21 2011 -0700 drm/i915: add fbc enable flag, but disable by default commit 8547920fc6f0d288fcc57ca705ccb2d00920fc72 Author: Feng, Boqun <boqun.feng@intel.com> Date: Thu Apr 28 17:15:33 2011 +0800 drm/i915: clean up unused ring_get_irq/ring_put_irq functions commit 5bfa1063a775836a84f97e4df863fc36e1f856ad Author: Feng, Boqun <boqun.feng@intel.com> Date: Mon May 16 16:02:39 2011 +0800 drm/i915: fix user irq miss in BSD ring on g4x commit 645c62a5e95a5f9a8e0d0627446bbda4ee042024 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed May 11 09:49:31 2011 -0700 drm/i915: split PCH clock gating init commit 28963a3eb5e2ae861995c2f7c15c7de982b3ce0e Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed May 11 09:42:30 2011 -0700 drm/i915: add Ivybridge clock gating init function commit 4593010b68247e6bed746da4e15f66f06e239e28 Author: Eric Anholt <eric@anholt.net> Date: Fri May 6 17:12:35 2011 -0700 drm/i915: Update the location of the ringbuffers' HWS_PGA registers for IVB The most likely fix is then disabling the FBC, which is consistent with the presentation of the bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.