Bug 41097 - [i915gm] GPU lockup: wait on disabled pipe
Summary: [i915gm] GPU lockup: wait on disabled pipe
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 17:28 UTC by Bryce Harrington
Modified: 2012-04-16 05:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
XorgLog.txt (35.54 KB, text/plain)
2011-09-21 17:29 UTC, Bryce Harrington
no flags Details
i915_error_state.txt (673.45 KB, text/plain)
2011-09-21 17:29 UTC, Bryce Harrington
no flags Details
CurrentDmesg.txt (7.60 KB, text/plain)
2011-09-21 17:29 UTC, Bryce Harrington
no flags Details
BootDmesg.txt (51.26 KB, text/plain)
2011-09-21 17:30 UTC, Bryce Harrington
no flags Details

Description Bryce Harrington 2011-09-21 17:28:17 UTC
Forwarding this bug from Ubuntu reporter Jon Arnold:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/839976

[Problem]
render error hit, after series of I/O errors on sr0.  The I/O errors first displayed during boot immediately after drm was initialized, the render error only later on.

[  187.890179] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  187.890187] sr 0:0:0:0: [sr0]  Sense Key : Illegal Request [current] 
[  187.890193] sr 0:0:0:0: [sr0]  Add. Sense: Read of scrambled sector without authentication
[  187.890203] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 08 6c 00 00 02 00
[  187.890214] end_request: I/O error, dev sr0, sector 8624
[  294.743986] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  294.743995] sr 0:0:0:0: [sr0]  Sense Key : Illegal Request [current] 
[  294.744040] sr 0:0:0:0: [sr0]  Add. Sense: Read of scrambled sector without authentication
[  294.744052] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 02 76 00 00 02 00
[  294.744063] end_request: I/O error, dev sr0, sector 2520
[  294.744070] quiet_error: 166 callbacks suppressed
[  294.744074] Buffer I/O error on device sr0, logical block 630
[  294.744079] Buffer I/O error on device sr0, logical block 631
[ 1969.223641] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[ 1969.224708] render error detected, EIR: 0x00000002
[ 1969.224712] memory refresh error:
[ 1969.224715] pipe A stat: 0x00020303
[ 1969.224718] pipe B stat: 0x00020302
[ 1972.913883] render error detected, EIR: 0x00000002
[ 1972.913890] memory refresh error:
[ 1972.913893] pipe A stat: 0x00020303
[ 1972.913895] pipe B stat: 0x00020302
[ 1997.884201] render error detected, EIR: 0x00000002
[ 1997.884218] memory refresh error:
[ 1997.884223] pipe A stat: 0x00020303
[ 1997.884225] pipe B stat: 0x00020302
[ 2000.488023] render error detected, EIR: 0x00000002
[ 2000.488038] memory refresh error:
[ 2000.488043] pipe A stat: 0x00020303
[ 2000.488045] pipe B stat: 0x00020302

[Original Description]
Occurred while watching an encrypted DVD in VLC. The video started lagging behind the audio as these crashes were popping up.

...later...
Actually, assuming it is the same crash, I'm getting these pop-up without watching a DVD, so that seems to be unrelated.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Chipset: i915gm
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Fri Sep  2 19:27:21 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
DuplicateSignature: [i915gm] GPU lockup  EIR: 0x00000002 render.IPEHR: 0x01000000 Ubuntu 11.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Gateway 2000 Device [107b:0610]
   Subsystem: Gateway 2000 Device [107b:0610]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
InterpreterPath: /usr/bin/python2.7
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway CX2619
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=a01d5c56-4777-481b-94c7-c8788fb2b204 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg             1:7.6+7ubuntu6
 libdrm2                  2.4.26-1ubuntu1
 xserver-xorg-video-intel 2:2.15.901-1ubuntu2
SourcePackage: xserver-xorg-video-intel
Title: [i915gm] False GPU lockup  EIR: 0x00000002 render.IPEHR: 0x01000000
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/12/2006
dmi.bios.vendor: Gateway
dmi.bios.version: 62.07
dmi.board.vendor: Gateway
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.version: Rev.1
dmi.modalias: dmi:bvnGateway:bvr62.07:bd04/12/2006:svnGateway:pnCX2619:pvr3402235:rvnGateway:rn:rvr:cvnGateway:ct8:cvrRev.1:
dmi.product.name: CX2619
dmi.product.version: 3402235
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1
Comment 1 Bryce Harrington 2011-09-21 17:29:38 UTC
Created attachment 51479 [details]
XorgLog.txt
Comment 2 Bryce Harrington 2011-09-21 17:29:49 UTC
Created attachment 51480 [details]
i915_error_state.txt
Comment 3 Bryce Harrington 2011-09-21 17:29:59 UTC
Created attachment 51481 [details]
CurrentDmesg.txt
Comment 4 Bryce Harrington 2011-09-21 17:30:10 UTC
Created attachment 51482 [details]
BootDmesg.txt
Comment 5 Chris Wilson 2012-04-16 05:19:23 UTC
commit 14667a4bde4361b7ac420d68a2e9e9b9b2df5231
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Apr 3 17:58:35 2012 +0100

    drm/i915: Finish any pending operations on the framebuffer before disabling
    
    Similar to the case where we are changing from one framebuffer to
    another, we need to be sure that there are no pending WAIT_FOR_EVENTs on
    the pipe for the current framebuffer before switching. If we disable the
    pipe, and then try to execute a WAIT_FOR_EVENT it will block
    indefinitely and cause a GPU hang.
    
    We attempted to fix this in commit 85345517fe6d4de27b0d6ca19fef9d28ac947c4a
    (drm/i915: Retire any pending operations on the old scanout when switching)
    for the case of mode switching, but this leaves the condition where we
    are switching off the pipe vulnerable.
    
    There still remains the race condition were a display may be unplugged,
    switched off by the core, a uevent sent to notify the DDX and the DDX
    may issue a WAIT_FOR_EVENT before it processes the uevent. This window
    does not exist if the pipe is only switched off in response to the
    uevent. Time to make sure that is so...

Along with the additional patches hinted at for SNA.


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.