Ubuntu
linux package

[i965gm] GPU lockup - needs git commit 85345517fe6d4de27b0d6ca19fef9d28ac947c4a

Bug #603064 reported by Matt Zimmerman
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
Critical
linux (Ubuntu)
Fix Released
High
Unassigned
Maverick
Invalid
High
Unassigned
Natty
Fix Released
High
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

This happened while watching a video in Totem.

ACTHD: 0x00000000
EIR: 0x00000000
EMR: 0xffffffcd
ESR: 0x00000000
PGTBL_ER: 0x00000000
IPEHR: 0x00000000
IPEIR: 0x00000000
INSTDONE: 0xffe5fafe
INSTDONE1: 0x000fffff
    busy: Projection and LOD
    busy: Bypass FIFO
    busy: Color calculator

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.11.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
Architecture: amd64
Chipset: i965gm
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1680x1050
 edid-base64: AP///////wAkTYcoAAAAAAAPAQOAIRV4CrylmFhViygkUFQAAAABAQEBAQEBAQEBAQEBAQEBHC+Q0GAaD0AgMBMAS88QAAAZRSeQ0GAaD0AgMBMAS88QAAAZAAAADwCzCjKzCigUAQAyDAAAAAAA/gBMUDE1NFcwMi1UTDA2AL8=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480
 edid-base64: AP///////wBMLeYDNjJXVCMSAQMONyJ4Kv4hqFM3riQRUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYAJlQhAAAaAAAA/QA4PB5REQAKICAgICAgAAAA/ABTeW5jTWFzdGVyCiAgAAAA/wBIVkRRODAwNDkwCiAgANc=
Date: Tue Jul 6 23:41:42 2010
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: 77c6dfe5
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 6465CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic root=UUID=305dde78-d20a-4248-aaf4-09447b7c5791 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [i965gm] GPU lockup 77c6dfe5
UserGroups:

dmi.bios.date: 01/21/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETB0WW (2.10 )
dmi.board.name: 6465CTO
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:bvr7LETB0WW(2.10):bd01/21/2008:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6465CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-6-generic

See original description
Revision history for this message
Matt Zimmerman (mdz) wrote :
Bryce Harrington (bryce)
tags: added: crash
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Bryce Harrington (bryce) wrote :

Forwarding this bug from Ubuntu reporter :
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/603064

[Problem]
GPU lockup while watching video in Totem. GPU dump attached

[Original Description]
This happened while watching a video in Totem.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.11.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
Architecture: amd64
Chipset: i965gm
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1680x1050
 edid-base64: AP///////wAkTYcoAAAAAAAPAQOAIRV4CrylmFhViygkUFQAAAABAQEBAQEBAQEBAQEBAQEBHC+Q0GAaD0AgMBMAS88QAAAZRSeQ0GAaD0AgMBMAS88QAAAZAAAADwCzCjKzCigUAQAyDAAAAAAA/gBMUDE1NFcwMi1UTDA2AL8=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480
 edid-base64: AP///////wBMLeYDNjJXVCMSAQMONyJ4Kv4hqFM3riQRUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYAJlQhAAAaAAAA/QA4PB5REQAKICAgICAgAAAA/ABTeW5jTWFzdGVyCiAgAAAA/wBIVkRRODAwNDkwCiAgANc=
Date: Tue Jul 6 23:41:42 2010
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: 77c6dfe5
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 6465CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic root=UUID=305dde78-d20a-4248-aaf4-09447b7c5791 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [i965gm] GPU lockup 77c6dfe5
UserGroups:

dmi.bios.date: 01/21/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETB0WW (2.10 )
dmi.board.name: 6465CTO
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:bvr7LETB0WW(2.10):bd01/21/2008:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6465CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
system: codename: maverick
 architecture: x86_64
 kernel: 2.6.35-6-generic

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36858)
BootDmesg.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36859)
CurrentDmesg.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36860)
Dependencies.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36861)
GdmLog.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36862)
GdmLog1.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36863)
GdmLog2.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36864)
Lspci.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36865)
Lsusb.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36866)
PciDisplay.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36867)
ProcCpuinfo.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36868)
ProcInterrupts.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36869)
ProcMaps.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36870)
ProcModules.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36871)
ProcStatus.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36872)
RelatedPackageVersions.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36873)
UdevDb.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36874)
UdevLog.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36875)
XorgConf.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36876)
XorgLog.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36877)
XorgLogOld.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36878)
Xrandr.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36879)
glxinfo.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36880)
i915_error_state.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36881)
setxkbmap.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36882)
xdpyinfo.txt

Revision history for this message
In , Bryce Harrington (bryce) wrote :

Created an attachment (id=36883)
xkbcomp.txt

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [i965gm] GPU lockup 77c6dfe5

I've forwarded this bug upstream to http://bugs.freedesktop.org/show_bug.cgi?id=28964 and subscribed you to it. Please follow up with them in case they need further information or wish you to test something.

Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
In , Chris Wilson (ickle) wrote :

batchbuffer at 0x0edac000:
0x0edac000: 0x09000000: MI_LOAD_SCAN_LINES_INCL
0x0edac004: 0x000004b0: dword 1
0x0edac008: 0x09000000: MI_LOAD_SCAN_LINES_INCL
0x0edac00c: 0x000004b0: dword 1
0x0edac010: 0x01800002: MI_WAIT_FOR_EVENT
0x0edac014: HEAD 0x54f08806: XY_SRC_COPY_BLT (rgb enabled, alpha enabled, src tile 1, dst tile 1)
0x0edac018: 0x03cc0780: format 8888, dst pitch 1920, clipping disabled
0x0edac01c: 0x00000000: dst (0,0)
0x0edac020: 0x04b00780: dst (1920,1200)
0x0edac024: 0x08f93000: dst offset 0x08f93000
0x0edac028: 0x00000000: src (0,0)
0x0edac02c: 0x00000780: src pitch 1920
0x0edac030: 0x07546000: src offset 0x07546000
0x0edac034: 0x02000000: MI_FLUSH
0x0edac038: 0x00000000: MI_NOOP
0x0edac03c: 0x05000000: MI_BATCH_BUFFER_END

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

Hmm, it is interesting how more careful the dri code is in handling the MI_WAIT_FOR_EVENT.

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

I've pushed addition checks from the dri WAIT_FOR_EVENT handling as they didn't appear to negatively impact my machine:

commit 272d1c14a39c32ade39b5a8b080a891f2b3d6e8e
Author: Chris Wilson <email address hidden>
Date: Fri Jul 9 10:41:19 2010 +0100

    video: apply the crtc box checks from dri.

    The dri code is much more careful in ensuring that the scan lines that
    is waits for are valid. Copy this code to video, with a bit of work this
    can be refactored, and perhaps even teach dri how to handle rotated
    front buffers.

    References:

      Bug 28964 - [i965gm] GPU infinite MI_WAIT_FOR_EVENT while watching video
                  in Totem
      https://bugs.freedesktop.org/show_bug.cgi?id=28964

However, these are just a set of extra sanity checks. It is not clear under what circumstances the machine froze so I cannot say whether this is the fix for the bug.

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

Clearing regression keyword, nothing in the report suggests that this bug has been recently introduced. If it can be narrowed down to particular commit (or range thereof) that would be most useful.

Revision history for this message
Robert Hooker (sarvatt) wrote : Re: [i965gm] GPU lockup 77c6dfe5

It looks like our friend bug #535640 is back as the patch fixing that is not upstream yet. Did the screen blank when this happened? Can you reproduce this if you change the "Put display to sleep when inactive for:" option in gnome-power-manager to never?

Revision history for this message
Bryce Harrington (bryce) wrote :

Or try setting it to put to sleep after 1 min and see if you can reproduce it more quickly?

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 603064] Re: [i965gm] GPU lockup 77c6dfe5

On Fri, Jul 09, 2010 at 03:37:27PM -0000, Robert Hooker wrote:
> It looks like our friend bug #535640 is back as the patch fixing that is
> not upstream yet. Did the screen blank when this happened? Can you
> reproduce this if you change the "Put display to sleep when inactive
> for:" option in gnome-power-manager to never?

At the time this happened, I was watching a film, so screen blanking should
have been suppressed at the time.

--
 - mdz

Revision history for this message
Geir Ove Myhr (gomyhr) wrote : Re: [i965gm] GPU lockup 77c6dfe5

Robert Hooker wrote in comment #3:
> It looks like our friend bug #535640 is back as the patch fixing that is not upstream yet.

I suppose we talk about:
SAUCE: drm/i915: don't change DRM configuration when releasing load detect pipe

It looks like that patch is not going to end up upstream. See [1] and [2]. The patch was removed from Maverick's git after Chase Douglas got someone to verify that it was no longer required [3].

[1]: http://lists.freedesktop.org/archives/intel-gfx/2010-July/007383.html
[2]: https://bugs.freedesktop.org/show_bug.cgi?id=27146#c19
[3]: https://lists.ubuntu.com/archives/kernel-team/2010-May/010602.html

Revision history for this message
madbiologist (me-again) wrote :

This might be fixed by http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=272d1c14a39c32ade39b5a8b080a891f2b3d6e8e

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

http://cgit.freedesktop.org/~ickle/drm-intel/log/?h=drm-intel-next contains a new check in hangcheck that should fix these as a last resort.

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

Repository moved:

git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git drm-intel-next

Bug Watch Updater (bug-watch-updater)
Changed in xserver-xorg-video-intel:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
madbiologist (me-again) wrote : Re: [i965gm] GPU lockup 77c6dfe5

I found this in the upstream kernel 2.6.37-rc1 changelog:

commit 4b60e5cb707aa1d44fd01680296a2caf45dd6fae
Author: Chris Wilson
Date: Sun Aug 8 11:53:53 2010 +0100

    drm/i915: Clear scanline waits after disabling the pipe.

    If we disable the pipe and the GPU is currently waiting on a scanline
    WAIT_FOR_EVENT, the GPU will hang. Fortunately, there is a magic bit
    which we can write on i915+ to break this wait after disabling the
    pipe.

    References:

      Bug 29252 - [Arrandale] Hung WAIT_FOR_EVENT when running rss-glx-skyrocket
      https://bugs.freedesktop.org/show_bug.cgi?id=29252

      Bug 28964 - [i965gm] GPU infinite MI_WAIT_FOR_EVENT while watching video in Totem
      https://bugs.freedesktop.org/show_bug.cgi?id=28964

    and many others.

    Signed-off-by: Chris Wilson
    Cc: Jesse Barnes

Revision history for this message
madbiologist (me-again) wrote :

@Matt Zimmerman - is this still happening with Ubuntu 11.04 "Natty Narwhal" alpha 1?

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 603064] Re: [i965gm] GPU lockup 77c6dfe5

On Wed, Dec 22, 2010 at 04:53:00AM -0000, madbiologist wrote:
> @Matt Zimmerman - is this still happening with Ubuntu 11.04 "Natty
> Narwhal" alpha 1?

It has never happened consistently, but I haven't seen it recently. The
system in question is also still running 10.10, so I don't have any new data
to add.

I would be happy to test boot 11.04 A1 on this system, but since I have no
reproducer, and it's not recurring on 10.10 at the moment, I don't think it
would help.

--
 - mdz

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [i965gm] GPU lockup 77c6dfe5

Upstream bug was solved with the following commit. I'm going to re-target this to the kernel team, so they can verify the fix is included for natty and sru it to maverick if appropriate. I am not seeing the git commit id in the ubuntu-maverick git tree, but maybe its commit id changed when it was backported.

commit 85345517fe6d4de27b0d6ca19fef9d28ac947c4a
Author: Chris Wilson <email address hidden>
Date: Sat Nov 13 09:49:11 2010 +0000

    drm/i915: Retire any pending operations on the old scanout when switching

    An old and oft reported bug, is that of the GPU hanging on a
    MI_WAIT_FOR_EVENT following a mode switch. The cause is that the GPU is
    waiting on a scanline counter on an inactive pipe, and so waits for a
    very long time until eventually the user reboots his machine.

    We can prevent this either by moving the WAIT into the kernel and
    thereby incurring considerable cost on every swapbuffers, or by waiting
    for the GPU to retire the last batch that accesses the framebuffer
    before installing a new one. As mode switches are much rarer than swap
    buffers, this looks like an easy choice.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=28964
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=29252
    Signed-off-by: Chris Wilson <email address hidden>
    Cc: <email address hidden>

description: updated
summary: - [i965gm] GPU lockup 77c6dfe5
+ [i965gm] GPU lockup - needs git commit
+ 85345517fe6d4de27b0d6ca19fef9d28ac947c4a
Changed in xserver-xorg-video-intel (Ubuntu Natty):
status: Triaged → Fix Released
Changed in xserver-xorg-video-intel (Ubuntu Maverick):
importance: Undecided → High
Revision history for this message
Bryce Harrington (bryce) wrote :

Kernel team - 85345517 needs cherrypicked and sru'd to maverick if it hasn't been already.

Changed in xserver-xorg-video-intel (Ubuntu Maverick):
status: New → Triaged
affects: xserver-xorg-video-intel (Ubuntu Maverick) → linux (Ubuntu Maverick)
Bug Watch Updater (bug-watch-updater)
Changed in xserver-xorg-video-intel:
importance: Critical → Unknown
status: Confirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in xserver-xorg-video-intel:
importance: Unknown → Critical
Revision history for this message
JC Hulce (soaringsky) wrote :

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bugtask for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

Changed in linux (Ubuntu Maverick):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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