Forwarding this bug from Ubuntu reporter Matt Zimmerman: http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/424055 [Problem] Karmic Intel GPU hang [Original Description] I'm afraid I don't have very much information about this, but I wanted to get a bug report open because it's potentially serious. I wasn't able to collect any additional information when I observed a hang, because I didn't have access to another system on the same network to ssh in (though based on my observations, I'm confident it was only the GPU. The system responded to sysrq+k, though the console was never properly restored). If there is another way other than ssh to get a text login on the system when it is in this state, I would like to know so that I can try it if it happens again. This appeared in syslog around the time of the hang, confirming it's a GPU lockup: Sep 3 15:46:24 atomicity kernel: [21000.796177] INFO: task i915/0:828 blocked for more than 120 seconds. Sep 3 15:46:24 atomicity kernel: [21000.796193] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 3 15:46:24 atomicity kernel: [21000.796206] i915/0 D c0805380 0 828 2 0x00000000 Sep 3 15:46:24 atomicity kernel: [21000.796227] ef44bf04 00000046 f707e000 c0805380 ef4ecdf8 c0805380 1b290057 000012f1 Sep 3 15:46:24 atomicity kernel: [21000.796256] c0805380 c0805380 ef4ecdf8 c0805380 00000000 000012f1 c0805380 eec77880 Sep 3 15:46:24 atomicity kernel: [21000.796283] ef4ecb60 ef52a414 ef52a418 ffffffff ef44bf30 c0567556 c073ce80 ef52a41c Sep 3 15:46:24 atomicity kernel: [21000.796310] Call Trace: Sep 3 15:46:24 atomicity kernel: [21000.796339] [<c0567556>] __mutex_lock_slowpath+0xc6/0x130 Sep 3 15:46:24 atomicity kernel: [21000.796356] [<c0567470>] mutex_lock+0x20/0x40 Sep 3 15:46:24 atomicity kernel: [21000.796424] [<f824e94a>] i915_gem_retire_work_handler+0x2a/0x70 [i915] Sep 3 15:46:24 atomicity kernel: [21000.796459] [<c015312e>] run_workqueue+0x6e/0x140 Sep 3 15:46:24 atomicity kernel: [21000.796515] [<f824e920>] ? i915_gem_retire_work_handler+0x0/0x70 [i915] Sep 3 15:46:24 atomicity kernel: [21000.796547] [<c0153288>] worker_thread+0x88/0xe0 Sep 3 15:46:24 atomicity kernel: [21000.796569] [<c0157930>] ? autoremove_wake_function+0x0/0x40 Sep 3 15:46:24 atomicity kernel: [21000.796590] [<c0153200>] ? worker_thread+0x0/0xe0 Sep 3 15:46:24 atomicity kernel: [21000.796604] [<c015763c>] kthread+0x7c/0x90 Sep 3 15:46:24 atomicity kernel: [21000.796618] [<c01575c0>] ? kthread+0x0/0x90 Sep 3 15:46:24 atomicity kernel: [21000.796635] [<c0103f17>] kernel_thread_helper+0x7/0x10 Architecture: i386 Date: Thu Sep 3 16:16:40 2009 DistroRelease: Ubuntu 9.10 MachineType: Dell Inc. Inspiron 1011 NonfreeKernelModules: wl Package: xorg 1:7.4+3ubuntu5 PccardctlIdent: PccardctlStatus: ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-9-generic root=UUID=0e0805c9-684a-4646-9724-954e05f7dd01 ro quiet splash ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-9.29-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3 libdrm2 2.4.12+git20090801.45078630-0ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu1 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu6 SourcePackage: xorg Tags: ubuntu-unr Uname: Linux 2.6.31-9-generic i686 dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. system: architecture: i686kernel: 2.6.31-9-generic
Created attachment 29202 [details] XorgLogOld.txt
Created attachment 29203 [details] XorgLog.txt
Created attachment 29204 [details] CurrentDmesg.txt
Created attachment 29205 [details] BootDmesg.txt
How to reproduce it? If there's no steady reproduce steps, nor gpu dump, I don't suggest this to be higher priority than other gpu hang bugs.
(In reply to comment #5) > How to reproduce it? > > If there's no steady reproduce steps, nor gpu dump, I don't suggest this to be > higher priority than other gpu hang bugs. > I'm no longer able to reproduce the problem. It's likely that Eric's mesa patch (about the relocation delta for WM surfaces) mentioned here fixed it: https://bugs.freedesktop.org/show_bug.cgi?id=23932
Good to know this. Let's close it. *** This bug has been marked as a duplicate of bug 23932 ***
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.