8086:2a42 [gm45] xserver completely freezes each time when executing paraview

[Andre Massing]

Binary package hint: xserver-xorg-video-intel

As the title says, X server crashes each time I start paraview and do some graphic operations.
Kubuntu Lucid is installed on a Dell Latitude E4300 (this problem occured already karmic on my machine).
syslog gives an entry:

 May 26 16:59:53 andre-laptop kernel: [ 1148.420262] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 26 16:59:53 andre-laptop kernel: [ 1148.420282] render error detected, EIR: 0x00000000
May 26 16:59:53 andre-laptop kernel: [ 1148.420527] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 197751 at 197749)
May 26 16:59:54 andre-laptop kernel: [ 1149.350258] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 26 16:59:54 andre-laptop kernel: [ 1149.350271] render error detected, EIR: 0x00000000
May 26 16:59:54 andre-laptop kernel: [ 1149.350327] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 197753 at 197749)
May 26 16:59:54 andre-laptop kernel: [ 1150.160252] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 26 16:59:54 andre-laptop kernel: [ 1150.160265] render error detected, EIR: 0x00000000
May 26 16:59:54 andre-laptop kernel: [ 1150.160340] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 197764 at 197749)
May 26 16:59:56 andre-laptop kdm[1010]: X server for display :0 terminated unexpectedly

After this event I have to restart my computer.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Wed May 26 17:28:52 2010
DkmsStatus: blcr, 0.8.2, 2.6.32-22-generic, x86_64: installed
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Dell Inc. Latitude E4300
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=960e7784-b9e7-4827-8f35-40acda9a423c ro splash
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 02/16/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D201R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/16/2009:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D201R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4300
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Dell Device [1028:024d]

[Stenten (stenten)]

Could you please try the current mainline kernel [1] and see if this fixes it? Download the *_all.deb headers file, the linux-headers for amd64 and the linux-image for amd64. And then install them in that order (just double-click them).

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/

[Andre Massing (massing)]

On 27. mai 2010 03:37, Stenten wrote:
> Could you please try the current mainline kernel [1] and see if this
> fixes it? Download the *_all.deb headers file, the linux-headers for
> amd64 and the linux-image for amd64. And then install them in that order
> (just double-click them).
>
> [1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/

I tried it out and although paraview and other heavily graphic card
using applications seems to run much smoother, I got a crash with
paraview. Paraview sometimes starts to hang, run very slowly with most
of the time results in a complete crash.
Syslog snippet indicates that as well:

May 27 12:32:09 andre-laptop acpid: 1 client rule loaded
May 27 12:32:10 andre-laptop kernel: [ 1488.707668] dell-wmi: Received
unknown WMI event (0x11)
May 27 12:32:11 andre-laptop kernel: [ 1489.890254]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 27 12:32:11 andre-laptop kernel: [ 1489.890268] render error
detected, EIR: 0x00000000
May 27 12:32:11 andre-laptop kernel: [ 1489.890325]
[drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5
(awaiting 202058 at 202001)
May 27 12:32:11 andre-laptop kernel: [ 1489.890350]
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on crtc
ffff8801178ca000
May 27 12:32:11 andre-laptop kernel: [ 1489.937426] dell-wmi: Received
unknown WMI event (0x11)
May 27 12:32:12 andre-laptop kernel: [ 1490.994480] dell-wmi: Received
unknown WMI event (0x11)
May 27 12:32:13 andre-laptop kernel: [ 1492.160255]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 27 12:32:13 andre-laptop kernel: [ 1492.160269] render error
detected, EIR: 0x00000000
May 27 12:32:13 andre-laptop kernel: [ 1492.160323]
[drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5
(awaiting 202059 at 202001)
May 27 12:32:14 andre-laptop kdm_greet[2320]: Cannot load
/usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
May 27 12:32:14 andre-laptop kernel: [ 1493.190256]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 27 12:32:14 andre-laptop kernel: [ 1493.190269] render error
detected, EIR: 0x00000000
May 27 12:32:14 andre-laptop kernel: [ 1493.190329]
[drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5
(awaiting 202061 at 202001)
May 27 12:32:15 andre-laptop kernel: [ 1494.000261]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 27 12:32:15 andre-laptop kernel: [ 1494.000275] render error
detected, EIR: 0x00000000
May 27 12:32:15 andre-laptop kernel: [ 1494.000331]
[drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5
(awaiting 202062 at 202001)
May 27 12:32:16 andre-laptop kernel: [ 1494.790249]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 27 12:32:16 andre-laptop kernel: [ 1494.790264] render error
detected, EIR: 0x00000000
May 27 12:32:16 andre-laptop kernel: [ 1494.790337]
[drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5
(awaiting 202067 at 202001)
May 27 12:32:17 andre-laptop kernel: [ 1495.570249]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck time...

[Stenten (stenten)]

Could you please boot into the Lucid kernel (2.6.32-22) and test the xorg-edgers PPA [1]? Hold down Shift while booting to get to grub to select the kernel. Alternately, you can remove the mainline through Synaptic; just search "2.6.34" and remove the three packages you installed. It's just important that you're not on the mainline kernel while testing xorg-edgers.

[1]: https://launchpad.net/~xorg-edgers/+archive/ppa

[Andre Massing (massing)]

Hi!
Sorry for my late response but I have been offline for a while. Did you want me to install *all* xorg packages from that repository? I did a first try just upgrading intel related packages and dependencies. But unfortunately this resulted into a freeze of mouse and keyboard, preventing me from logging in from kdm.
These are the packages I upgraded:

[OPPGRADER] intel-gpu-tools 1.0.2+git20100324-0ubuntu1 -> 1.0.2+git20100515-0ubuntu0sarvatt~lucid
[OPPGRADER] libdrm-dev 2.4.18-1ubuntu3 -> 2.4.20+git20100527.607e228c-0ubuntu0sarvatt2~lucid
[OPPGRADER] libdrm-intel1 2.4.18-1ubuntu3 -> 2.4.20+git20100527.607e228c-0ubuntu0sarvatt2~lucid
[OPPGRADER] libdrm-nouveau1 2.4.18-1ubuntu3 -> 2.4.20+git20100527.607e228c-0ubuntu0sarvatt2~lucid
[OPPGRADER] libdrm-radeon1 2.4.18-1ubuntu3 -> 2.4.20+git20100527.607e228c-0ubuntu0sarvatt2~lucid
[OPPGRADER] libdrm2 2.4.18-1ubuntu3 -> 2.4.20+git20100527.607e228c-0ubuntu0sarvatt2~lucid
[OPPGRADER] libx11-data 2:1.3.2-1ubuntu3 -> 2:1.3.3+git20100513.fd82552d-0ubuntu0sarvatt~lucid
[OPPGRADER] mesa-utils 7.7.1-1ubuntu3 -> 7.9.0~git20100520.f4905256-0ubuntu0sarvatt2~lucid
[OPPGRADER] xserver-common 2:1.7.6-2ubuntu7 -> 2:1.8.1+git20100521+server-1.8-branch.a8de0866-0ubuntu0sarvatt~lucid
[OPPGRADER] xserver-xorg-core 2:1.7.6-2ubuntu7 -> 2:1.8.1+git20100521+server-1.8-branch.a8de0866-0ubuntu0sarvatt~lucid
[OPPGRADER] xserver-xorg-video-intel 2:2.9.1-3ubuntu5 -> 2:2.11.0+git20100527.73111cf2-0ubuntu0sarvatt~lucid
[OPPGRADER] xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu5 -> 1:0.0.16+git20100513.4b8f1a08-0ubuntu0sarvatt2~lucid

I haven't yet filed a bug report against this issue, since I was not sure whether I need also to update all the other xorg packages. But at least dependency resolution in aptitude did not indicate that I have to update them as well.

[Stenten (stenten)]

Please read the "Importance notice" at the bottom of the description for the xorg-edgers PPA.
Installation Instructions:
sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get update && sudo apt-get install ppa-purge
sudo apt-get upgrade

To revert:
sudo ppa-purge ppa:xorg-edgers/ppa

[Andre Massing (massing)]

Hi! I just installed all packages from xorg-edgers PPA as recommended and tested it. Error remains. Xserver hangs when I move cutplanes around in paraview, with restart of the xserver and almost complete freeze afterwards (Only terminals display 1 to 5 remained alive). Same log messages as before.
Are there any other information/configurations I could provide/check? Thanks for the suggestions and help!

[Stenten (stenten)]

Why yes, there is :)

But first, we need a little more background information: What exactly do you mean by "crash"? Exactly what screens do you see? Also, can you switch to a TTY with Ctrl+Alt+F1 when it crashes? If not, can you kill X with Alt+SysRq+k?

[Andre Massing (massing)]

Hi!

Sorry for my late reply, others things kept me from more testing. So here is the (hopefully) better report.
As I wrote my system crashes 100% "reliably" each time I use paraview, load a file, add a cutplane in paraview and try to rotate the object. Crashes means the following phases:
1. Mouse cursor starts to stutter, indicate high workload.
2. xserver/KDM dies (black screen)
3. Tries to restart xserver/kdm. I see the typical load cursor symbol (when kdm is usually starting) flickering on an otherwise black screen.
4. Loading stops and system freezes completely. Just seeing a black screen and a terminal cursor in the upper left corner.
Not possible to change to any other TTY from 1-6. None of the magic key combination works (I tested them also during a normal session, and then they work).
BTW, I get also occasionally a xserver restart when I change to TTY 1-6 (which caused that I had to write this comment twice :)

Use me at your guinea pig and tell if there is more I can test/crash :) or other information you need.
Cheers,
Andre

[Andre Massing (massing)]

Hi! I just want to add that the same bug also occurs on a Ubuntu installation (gnome-desktop). BTW, do you need any further (and what kind of) information (since this bug is still marked as incomplete)?

Cheers,
Andre

[Stenten (stenten)]

Please recreate the issue with the xorg-edgers PPA packages and the latest current mainline kernel [1] (installation instructions here [2]).

After you recover (i.e. reboot), upload /var/log/kern.log and /var/log/Xorg.0.log.old. Also check
cat /sys/kernel/debug/dri/0/i915_error_state
If there's anything in there other than "no error state collected", upload "/sys/kernel/debug/dri/0/i915_error_state" too.

[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[2]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds

[Andre Massing (massing)]

I proceed as you wrote. Summary: With linux-image-2.6.35-999-generic_2.6.35-999.201006301005_amd64.deb as the latest mainline kernel and xorg-edgers I almost got the same error, desktop starts to hang after paraview action. No windows and keyboard interaction possible, only the mouse pointer can slowly be moved. But this time Alt+SysRq+k worked and kill the xserver. Therefore I could save the sys/kernel/debug/dri/0/ output. Attachments follow...

[timo skrempel (timoskrempel)]

I am having the same problem running 2.6.35-19 in maverick beta when starting paraview. I can switch to a TTY too.

[Jared Klingenberger (itsjareds)]

I am having the same problem when running any graphics intense program on 2.6.35-24-generic kernel, Maverick. I am able to switch to a TTY (albeit very slowly, and the TTY is being spammed with that error). However, even after running `sudo restart gdm' I cannot get to a functional GUI - black screen.

I tried updating to xorg-edgers PPA; however, these new drivers leave me not able to start Compiz and the window list, gnome-workspace, and "Show desktop" panel applets crash. I have to stop the program "wnck-applet" because it is taking up a lot of processing power due to what seems to be an infinite loop of creating new windows that say "Starting ..."

When I switch to TTY with the xorg-edgers drivers, I get the same log output as previously mentioned (hangcheck timer elapsed, render head ctl reset to 0). I would really appreciate a fix to this bug.

[Bryce Harrington (bryce)]

X didn't crash, it's a gpu lockup in the kernel drm code. Refiling.

[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

[penalvch (penalvch)]

Andre Massing, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

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

[Andre Massing (massing)]

Hi,

unfortunately I don't use/owe that particular machine any more (and have now a machine with a different graphic card) and therefore cannot test whether this bug still occurs.
Best,
Andre