[sandybridge-m-gt2] False GPU lockup IPEHR: 0x01800100 IPEHR: 0x0b140001

Bug #1102390 reported by Timo Jyrinki
64
This bug affects 10 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
Medium
xserver-xorg-video-intel (Ubuntu)
Fix Released
High
Unassigned

Bug Description

My first (soft) crash during a couple of weeks of raring usage. Happens when attaching laptop to my HDMI monitor _and_ then closing the lid so that the laptop display goes off. System continues to work, with the exception that now X.org consumes 100% CPU time and graphics drawing is very slow.

Notes:
- did not happen earlier. I ran updates today (kernel + unity etc, I did the previous update on Thursday or Friday). now happens consistently, and seemingly even if I boot with the older 3.8.0-0 kernel which makes it a bit mysterious but still some sort of regression
- does not happen with UXA
- happens with 2.20.19 as well

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.20.18-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Chipset: sandybridge-m-gt2
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Mon Jan 21 14:45:26 2013
DistUpgraded: 2013-01-10 16:15:20,623 DEBUG enabling apt cron job
DistroCodename: raring
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x01800100 IPEHR: 0x0b140001 Ubuntu 13.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1427]
InstallationDate: Installed on 2012-03-16 (310 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
InterpreterPath: /usr/bin/python3.3
MachineType: ASUSTeK Computer Inc. UX31E
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 i915.semaphores=1 pcie_aspm=force vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu4
 libdrm2 2.4.41-0ubuntu1
 xserver-xorg-video-intel 2:2.20.18-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Title: [sandybridge-m-gt2] False GPU lockup IPEHR: 0x01800100 IPEHR: 0x0b140001
UpgradeStatus: Upgraded to raring on 2013-01-10 (10 days ago)
UserGroups:

XorgConf:
 Section "Device"
  Identifier "Configured Video Device"
  Driver "intel"
  Option "AccelMethod" "sna"
 EndSection
dmi.bios.date: 06/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.9~daily13.01.17-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.41-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.18-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1
xserver.bootTime: Mon Jan 21 14:14:47 2013
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 intel(0): Detected a hung GPU, disabling acceleration.
 intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.1.901-0ubuntu1
xserver.video_driver: intel

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
tags: removed: need-duplicate-check
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

try with 2.20.19 once it's built

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

nevermind, it's a kernel regression

Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → High
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
status: New → Triaged
description: updated
Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
status: Unknown → Confirmed
description: updated
Changed in xserver-xorg-video-intel:
status: Confirmed → Incomplete
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Fixed upstream, was a regression in the DDX driver.

Changed in linux (Ubuntu):
status: Triaged → Invalid
importance: High → Undecided
Timo Aaltonen (tjaalton)
no longer affects: linux (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-intel - 2:2.20.19-0ubuntu2

---------------
xserver-xorg-video-intel (2:2.20.19-0ubuntu2) raring; urgency=low

  * upstream-snapshot-778dba90c.diff: Patch to update to current git
    master (LP: #1102390).
 -- Timo Aaltonen <email address hidden> Thu, 24 Jan 2013 10:22:41 +0200

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Fix Released
Changed in xserver-xorg-video-intel:
status: Incomplete → Fix Released
Revision history for this message
Stan Schymanski (schymans) wrote :

I have all updates installed and my system is unusable because of recurrent gpu lockups. Could someone guide me how to implement the alleged fixes?

Revision history for this message
Chris Wilson (ickle) wrote :

If you have an updated raring system, then you are no longer hitting the same bug.

Revision history for this message
Stan Schymanski (schymans) wrote :

Sorry, I didn't realise that raring is now considered the most up-to-date release. I meant all updates installed for quantal.
Thanks also for your help regarding my related bug report: https://bugs.launchpad.net/bugs/1153587
I'll try updating the kernel tonight.

Revision history for this message
Stan Schymanski (schymans) wrote :

I upgraded to Kernel 3.8.2, but it didn't take more than two minutes after reboot before the GPU lockup crash report reappeared. And it just keeps going...
I suppose it is a different bug, then.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.