Bug#541117: xserver-xorg-video-intel: high CPU usage after 2.7.1-1 - 2.8.0-1 upgrade

2009-08-20 Thread Brice Goglin
Andrew Pimlott wrote:
 Package: xserver-xorg-video-intel
 Version: 2:2.8.0-1
 Severity: important

 After upgrading from 2.7.1-1, firefox is terribly slow and causes xorg
 to pin the CPU for several seconds when (for example) switching tabs.
 I'm running kernel linux-image-2.6.30-1-686 on a Thinkpad X40.  I've
 looked through the other bugs, and I don't think my problem matches any
 of them.

 I also observe that when I resume from suspend to ram, my background is
 corrupt.  And I've had a couple crashes.  None of this happened with
 2.7.1-1.

 2:2.8.0-2 has the same behavior.

 Finding a hint in bug 538283, I tried adding the i915 module with
 modeset=1.  I made the changes in /etc/modules and
 /etc/modprobe.d/local.conf and rebooted.  The effect on the text VCs was
 obvious, but when I tried to startx, it hung with a blank screen.
   

According to errors in your log, something's going bad with DRM. Does
this log come from a second X server while another X server was already
using the DRM device?

Brice


 (EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
 (EE) intel(0): Failed to become DRM master.
 [...]
 (WW) intel(0): DRI2: failed to open drm device
 (**) intel(0): Framebuffer compression enabled
 (**) intel(0): Tiling enabled
 (**) intel(0): SwapBuffers wait enabled
 (EE) intel(0): Failed to initialize kernel memory manager
 (==) intel(0): VideoRam: 131072 KB
 (II) intel(0): Attempting memory allocation with tiled buffers.
 (WW) intel(0): xf86AllocateGARTMemory: allocation of 1536 pages failed
   (Cannot allocate memory)
 (WW) intel(0): Allocation error, framebuffer compression disabled
 (WW) intel(0): xf86AllocateGARTMemory: allocation of 10 pages failed
   (Cannot allocate memory)
 (II) intel(0): Tiled allocation successful.
 (II) intel(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x
 (II) UXA(0): Driver registered support for the following operations:
 (II) solid
 (II) copy
 (==) intel(0): Backing store disabled
 (==) intel(0): Silken mouse enabled
 (II) intel(0): Initializing HW Cursor
 (WW) intel(0): drmSetMaster failed: Bad file descriptor
   




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#541117: xserver-xorg-video-intel: high CPU usage after 2.7.1-1 - 2.8.0-1 upgrade

2009-08-20 Thread Andrew Pimlott
On Thu, Aug 20, 2009 at 08:56:16AM +0200, Brice Goglin wrote:
 According to errors in your log, something's going bad with DRM. Does
 this log come from a second X server while another X server was already
 using the DRM device?

Damn, I don't know why I didn't notice that.  No, it was the only X
server running.  But I took a look at my configuration and noticed that
I had

Disable dri

because of bug 525123.  I don't know what dri has to do with drm, but
seeing that they have the first two letters I decided to comment that
out and try running 2.8 again.  Now, it performs well again!  And, I
don't see any of the issues from bug 525123 either (even though I can't
remember quite what that looked like).  In sum, on my X40:

2.7.1   2.8.0
empty configbug 525123  :-)
Disable dri   :-) bug 541117

I'm attaching two diffs of the log files.  2.7.1-2.8.0.diff compares
2.7.1 with 2.8.0, both with Disable dri.  (I should have run this diff
before I filed the bug, sorry.)  enable_dri.diff compares 2.8.0 with
Disable dri and without.

Thanks for your help!

Andrew
--- /var/log/Xorg.0.log	2009-08-20 08:05:19.0 -0700
+++ /var/log/Xorg.0.log.old	2009-08-20 08:02:58.0 -0700
@@ -11,7 +11,7 @@
 Markers: (--) probed, (**) from config file, (==) default setting,
 	(++) from command line, (!!) notice, (II) informational,
 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(==) Log file: /var/log/Xorg.0.log, Time: Thu Aug 20 08:05:15 2009
+(==) Log file: /var/log/Xorg.0.log, Time: Thu Aug 20 08:02:44 2009
 (==) Using config file: /etc/X11/xorg.conf
 (==) No Layout section.  Using the first Screen section.
 (==) No screen section available. Using defaults.
@@ -111,7 +111,7 @@
 (II) LoadModule: intel
 (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
 (II) Module intel: vendor=X.Org Foundation
-	compiled for 1.6.3, module version = 2.7.1
+	compiled for 1.6.2.901, module version = 2.8.0
 	Module class: X.Org Video Driver
 	ABI class: X.Org Video Driver, version 5.0
 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
@@ -119,7 +119,8 @@
 	E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
 	965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
 	Mobile IntelĀ® GM45 Express Chipset,
-	Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
+	Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41, IGDNG_D,
+	IGDNG_M
 (II) Primary Device is: PCI 0...@00:02:0
 (II) resource ranges after xf86ClaimFixedResources() call:
 	[0] -1	0	0x - 0x (0x1) MX[B]
@@ -149,6 +150,8 @@
 (II) Loading sub module ramdac
 (II) LoadModule: ramdac
 (II) Module ramdac already built-in
+(EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
+(EE) intel(0): Failed to become DRM master.
 (II) intel(0): Creating default Display subsection in Screen section
 	Default Screen Section for depth/fbbpp 24/32
 (==) intel(0): Depth 24, (--) framebuffer bpp 32
@@ -157,9 +160,9 @@
 (II) intel(0): Integrated Graphics Chipset: Intel(R) 855GME
 (--) intel(0): Chipset: 852GM/855GM
 (--) intel(0): Linear framebuffer at 0xE000
-(--) intel(0): IO registers at addr 0xD000
+(--) intel(0): IO registers at addr 0xD000 size 524288
 (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
-(==) intel(0): Using EXA for acceleration
+(II) intel(0): No SDVO device is found in VBT
 (II) intel(0): 2 display pipes available.
 (II) Loading sub module ddc
 (II) LoadModule: ddc
@@ -179,14 +182,14 @@
 (II) LoadModule: sil164
 (II) Loading /usr/lib/xorg/modules/drivers//sil164.so
 (II) Module sil164: vendor=X.Org Foundation
-	compiled for 1.6.3, module version = 1.0.0
+	compiled for 1.6.2.901, module version = 1.0.0
 	ABI class: X.Org Video Driver, version 5.0
 (II) intel(0): I2C bus DVOI2C_E initialized.
 (II) Loading sub module ch7xxx
 (II) LoadModule: ch7xxx
 (II) Loading /usr/lib/xorg/modules/drivers//ch7xxx.so
 (II) Module ch7xxx: vendor=X.Org Foundation
-	compiled for 1.6.3, module version = 1.0.0
+	compiled for 1.6.2.901, module version = 1.0.0
 	ABI class: X.Org Video Driver, version 5.0
 (II) intel(0): I2C bus DVOI2C_E removed.
 (II) intel(0): I2C bus DVOI2C_E initialized.
@@ -194,7 +197,7 @@
 (II) LoadModule: ivch
 (II) Loading /usr/lib/xorg/modules/drivers//ivch.so
 (II) Module ivch: vendor=X.Org Foundation
-	compiled for 1.6.3, module version = 1.0.0
+	compiled for 1.6.2.901, module version = 1.0.0
 	ABI class: X.Org Video Driver, version 5.0
 (II) intel(0): I2C bus DVOI2C_E removed.
 (II) intel(0): I2C bus DVOI2C_B initialized.
@@ -202,7 +205,7 @@
 (II) LoadModule: tfp410
 (II) Loading /usr/lib/xorg/modules/drivers//tfp410.so
 (II) Module tfp410: vendor=X.Org Foundation
-	compiled for 1.6.3, module version = 1.0.0
+	compiled for 1.6.2.901, module version = 1.0.0
 	ABI class: X.Org Video Driver, version 5.0
 (II) intel(0): I2C bus DVOI2C_B removed.
 (II) intel(0): I2C bus DVOI2C_E initialized.
@@ -210,13 +213,12 @@
 (II) 

Bug#541117: xserver-xorg-video-intel: high CPU usage after 2.7.1-1 - 2.8.0-1 upgrade

2009-08-11 Thread Andrew Pimlott
Package: xserver-xorg-video-intel
Version: 2:2.8.0-1
Severity: important

After upgrading from 2.7.1-1, firefox is terribly slow and causes xorg
to pin the CPU for several seconds when (for example) switching tabs.
I'm running kernel linux-image-2.6.30-1-686 on a Thinkpad X40.  I've
looked through the other bugs, and I don't think my problem matches any
of them.

I also observe that when I resume from suspend to ram, my background is
corrupt.  And I've had a couple crashes.  None of this happened with
2.7.1-1.

2:2.8.0-2 has the same behavior.

Finding a hint in bug 538283, I tried adding the i915 module with
modeset=1.  I made the changes in /etc/modules and
/etc/modprobe.d/local.conf and rebooted.  The effect on the text VCs was
obvious, but when I tried to startx, it hung with a blank screen.

BTW, the Xorg.0.log file included below is actually Xorg.0.log.old,
since I'm running the downgraded X now.  It is the log file that
corresponds with the bad behavior.

Any hints on where to look?

Thanks,
Andrew

PS.  How do you downgrade these days, since snapshot.debian.net is
stale?  I found a source package at Ubuntu launchpad, but it was a pain.

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 2008-10-22 10:53 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1689976 2009-08-06 09:55 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)

/var/lib/x11/xorg.conf.md5sum does not exist.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 865 2009-05-10 10:55 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type man xorg.conf at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section Module
# bugs.debian.org/525123
Disable dri
EndSection

Section Device
Identifier  Configured Video Device
EndSection

# Mouse wheel emulation now configured in
# /etc/hal/fdi/policy/20thirdparty/10-x11-evdev.fdi
# Progress!


Xorg X server log files on system:
-rw-rw-r-- 1 root root 67514 2006-01-12 14:22 /var/log/Xorg.2.log
-rw-rw-r-- 1 root root 36581 2009-05-11 12:18 /var/log/Xorg.1.log
-rw-rw-r-- 1 root root 53946 2009-08-11 11:00 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log.old:

X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian
Current Operating System: Linux apple 2.6.30-1-686 #1 SMP Mon Aug 3 16:18:30 
UTC 2009 i686
Build Date: 06 August 2009  04:49:57PM
xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Tue Aug 11 10:21:00 2009
(==) Using config file: /etc/X11/xorg.conf
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |--Screen Default Screen Section (0)
(**) |   |--Monitor default monitor
(==) No device specified for screen Default Screen Section.
Using the first device section listed.
(**) |   |--Device Configured Video Device
(==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to /usr/lib/xorg/modules
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable 
AllowEmptyInput.
(II) Loader magic: 0x6c0
(II) Module ABI