[i965q] Kubuntu jaunty xorg intel driver crashes

[Thiago Galesi]

Binary package hint: xserver-xorg-video-intel

This began with the update to Jaunty

xserver-xorg-video-intel

Machine starts, kdm starts, everything is (almost) fine. Icons get corrupted (especially in the notification area), duplicate icons, corrupted, etc

But the real problem starts when trying to go to a console and then coming back (or starting kdm). X dies upon restarting.

Disabling DRI/DRI2 doesnt' work, the only thing that worked was setting NoAccell option

I'll try to reproduce the problem and get the Xorg.0.log from when the problem happens.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.24-19-server (buildd@terranova) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 23:54:28 UTC 2008
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.24-19-server i686
glxinfo:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82Q963/Q965 Memory Controller Hub [8086:2990] (rev 02)
     Subsystem: Micro-Star International Co., Ltd. Device [1462:7276]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02)
     Subsystem: Micro-Star International Co., Ltd. Device [1462:7276]

[Bryce Harrington (bryce)]

You mentioned kdm - are you using kubuntu?

[Thiago Galesi (thiagogalesi)]

Correct

(even though it doesn't look like a specific KDE problem)

[Bryce Harrington (bryce)]

> (even though it doesn't look like a specific KDE problem)

What makes you conclude this?

We are moving to the UXA acceleration architecture for Karmic, and this bug needs to be re-tested to see if it still occurs there. Would you please install and test the 2.7.0 driver and reproduce the bug, and let us know ASAP? A PPA with a Jaunty version of this driver is available at: https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/, or you can update to Karmic and test that. Thanks ahead of time, and let us know either way.

[Thiago Galesi (thiagogalesi)]

OK, I tested this:

ii xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1

With the standart xorg.conf , xorg doesn't crash, but I get a black screen on kdm (only with a functioning mouse cursor)

On reverting to the 'good' Xorg.conf and restarting kdm, the machine crashed. But then it worked with the good Xorg. (some of the problem seem to be with initialization)

[Thiago Galesi (thiagogalesi)]

Take a look at this screenshot

uptime
 13:23:47 up 7 days, 3:59,

It started going flaky like this today (and every 7 days approximately)

[Albert Damen (albrt)]

ProcVersion: Linux version 2.6.24-19-server

You are using a hardy server kernel, which does not have GEM.
Can you please install the jaunty generic kernel (2.6.28-11-generic) and boot and test with that kernel?

[Thiago Galesi (thiagogalesi)]

Ok, testing under way

2.6.28-13-server is good?? (it has to be server b/c of 4Gb of RAM and not x86_64)

[Robert Hooker (sarvatt)]

Unfortunately there is no support for GEM on any PAE kernel yet (CONFIG_HIGHMEM64G=y which the i386 -server kernels use). Switching to x64 which does not need PAE or using -generic with reduced memory will *drastically* improve your experience with it until that changes. My suggestion instead would be to look into something such as installing the 2.4.1 driver this PPA if you want to stick with i386 PAE since the newer drivers really are reliant on GEM.

https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-retro

[Thiago Galesi (thiagogalesi)]

Robert, this looks like something I can live with.

I would really like to use the -generic kernel or x64 but this is my work machine :(

I'll test the x-retro driver then.

[Geir Ove Myhr (gomyhr)]

This bug report has been inactive for quite some time and in the meantime Ubuntu has moved along. I hope the reported problem has been resolved in the current version of Ubuntu. If it has not and there are people willing to follow up with information collecting and testing, it is best to file a new bug report with the latest Ubuntu development version (10.04 still works, but soon 10.10 is better), using the ubuntu-bug command if possible. Feel free to mention the bug number of this bug.

We are sorry that we are not always have the capacity to look at all reported bugs in a timely manner. Occasionally we have to purge old bug reports where no progress has been made, whether it is due to reporter not being able to respond or lack of manpower on the Ubuntu side, in order to keep our list of "active" bugs current. Sorry for the inconvenience this may cause.

Here are a few tips that will make it easier for triagers and developers to process your bug:
* Read https://wiki.ubuntu.com/X/Reporting
* Browse https://wiki.ubuntu.com/X and see if there is some relevant information for you problem
* Respond quickly to questions from triagers
* Try changing things to see if the behaviour changes, e.g.
  * A new mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D (more information at https://wiki.ubuntu.com/KernelTeam/MainlineBuilds)
  * The xorg-edgers PPA: https://launchpad.net/~xorg-edgers/+archive/ppa
  * Various options in `/etc/X11/xorg.conf` (see `man intel`)
* Browse other bug reports to see if you find a similar one and provide the information that is being asked for there.