Bug 35870 - [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x7a005502)
Summary: [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x7a005502)
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-01 05:40 UTC by Timo Aaltonen
Modified: 2012-10-21 14:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
register dump from before hooking up a monitor (7.17 KB, text/plain)
2011-04-13 02:28 UTC, Timo Aaltonen
no flags Details

Description Timo Aaltonen 2011-04-01 05:40:58 UTC
Forwarding this bug from Ubuntu reporter Matt Zimmerman:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/747205

[Problem]
[arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x7a005502)

[Original Description]
Steps:
1. be running maverick
2. run update-manager -d and upgrade to beta 1
3. reboot as directed
4. in GDM, log into the default desktop session

Result:
The screen turns black, and there is no mouse pointer, etc...

This happened on the first boot after upgrading to Natty
GPU signature is similar to bug 721086

I filed this by manually running /usr/share/apport/apport-gpu-error-intel.py in order to get the GPU dump etc. I do not know whether the GPU was actually hung or not.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Chipset: arrandale
Date: Fri Apr  1 12:56:57 2011
DistroCodename: natty
DistroVariant: ubuntu
DuplicateSignature: (ESR: 0x00000001 IPEHR: 0x7a005502)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: LENOVO 5129CTO
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcCwd: /home/jane
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=52f3f8dd-ab0d-4f3b-8cef-9bc54492e659 ro quiet splash vt.handoff=7
RelatedPackageVersions:
xserver-xorg             1:7.6+4ubuntu1
libdrm2                  2.4.23-1ubuntu5
xserver-xorg-video-intel 2:2.14.0-4ubuntu5
SourcePackage: xserver-xorg-video-intel
Title: [arrandale] GPU lockup (ESR: 0x00000001 IPEHR: 0x7a005502)
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)
UserGroups:

dmi.bios.date: 09/15/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET53WW (1.23 )
dmi.board.name: 5129CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET53WW(1.23):bd09/15/2010:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5129CTO
dmi.product.version: ThinkPad X201s
dmi.sys.vendor: LENOVO
i915_error_state: no error state collected
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1
Comment 1 Timo Aaltonen 2011-04-01 06:04:05 UTC
apparently this only happens with an external monitor hooked up.
Comment 2 Chris Wilson 2011-04-01 07:12:09 UTC
I think the telling comment from the lp bug is:

There is a lot of noise in CurrentDmesg.txt because rtl8192 is spamming the kernel log, but this is the first abnormal drm message:

[ 4425.992922] [drm:i915_gem_do_execbuffer] *ERROR* Object ffff8801b0d60600 [handle 639, index 1] appears more than once in object list

for which the fix is libdrm-2.4.24:

commit 36d4939343d8789d9066f7245fa2d4fe69119dd8
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Feb 14 09:39:06 2011 +0000

    intel: Remember named bo
    
    ... and if asked to open a bo by the same global name, return a fresh
    reference to the previously allocated buffer.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 3 Bryce Harrington 2011-04-07 01:55:55 UTC
Original reporter updated to this version and still has the same problem.

"""
Re-opening this because the original problem still exists (fully updated
Natty beta as of 6 April).  If I boot with external monitor attached,
the screen of laptop and monitor turn black as soon as I log in.  If I
boot without external monitor, I can log in and the desktop appears as
expected.  If I plug an external monitor or projector in after the
desktop is running, then it either turns black or a blinking solid dark
red colour.
"""
Comment 4 Chris Wilson 2011-04-11 23:09:13 UTC
I note that the bug was re-opened not by the original reporter, but by someone else reporting a different issue without any logs.
Comment 5 Timo Aaltonen 2011-04-11 23:17:03 UTC
I'll ask for a new set of logs to attach.
Comment 6 Bryce Harrington 2011-04-12 11:21:38 UTC
(In reply to comment #4)
> I note that the bug was re-opened not by the original reporter, but by someone
> else reporting a different issue without any logs.

No, it's the same issue and same original reporter actually, just both me and Timo (and Matt) are all assisting her.  The original reporter in the downstream bug report is Jane Silber.
Comment 7 Chris Wilson 2011-04-12 11:40:41 UTC
My apologies for the confusion.
Comment 8 Timo Aaltonen 2011-04-13 02:28:11 UTC
Created attachment 45570 [details]
register dump from before hooking up a monitor

This is a register dump before using the external monitor, and it's identical to the one _after_..
Comment 9 Chris Wilson 2012-04-20 08:33:40 UTC
Looking for the error-state, dmesg and Xorg.0.log that is associated with this bug.
Comment 10 Chris Wilson 2012-10-21 14:29:52 UTC
Timeout. Please do reopen if you can still reproduce the issue and help us diagnose the problem, thanks.


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.