[Needs 2.6.38] [sandybridge] GPU lockup (IPEHR: 0x680b0000)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
xserver-xorg-video-intel (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
This bug seems to be particular to Sandybridge hardware. The IPEHR values seem to vary from freeze to freeze, but seem to not be random. The value 0x68b0000 has been seen in a few different reports by different people, along with 0x78170003 and one or two other codes.
Here is an example sequence from one reporter on a particular system:
#733206 (IPEHR: 0x78170003)
#733208 (IPEHR: 0x680b0000)
#733209 (IPEHR: 0x78170003)
#733324 (IPEHR: 0x680b0000)
His description: "The GPU lockups really soon. The time between the login and the lockup is between a few seconds and a few minutes. Opening Nautilus and trying to do something there is a guarantee for catching a lockup."
[Original Bug Report]
I believe this is the same bus as #715122, but after the last update (#142 from 2011-02-11)
[ 482.078037] do_trap: 6 callbacks suppressed
[ 482.078042] intel_gpu_top[1931] trap divide error ip:4016bf sp:7fff09c33610 error:0 in intel_gpu_
[ 750.170912] [drm:i915_
[ 750.172237] [drm:i915_
[ 750.231061] divide error: 0000 [#1] SMP
[ 750.231079] last sysfs file: /sys/devices/
[ 750.231101] CPU 0
[ 750.231107] Modules linked in: binfmt_misc parport_pc ppdev dm_crypt snd_hda_codec_hdmi snd_hda_
[ 750.231243]
[ 750.231249] Pid: 5, comm: kworker/u:0 Not tainted 2.6.38-3-generic #30-Ubuntu DH67BL/
[ 750.231272] RIP: 0010:[<
[ 750.231308] RSP: 0018:ffff88020f
[ 750.231324] RAX: 0000000000000000 RBX: 00000000000005dc RCX: 0000000000000000
[ 750.231344] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88020b32a000
[ 750.231363] RBP: ffff88020f4eb8c0 R08: 0000000000000004 R09: 0000000000000000
[ 750.231383] R10: 00000000000005dc R11: ffff88020f4eb92c R12: ffff88020f4eb928
[ 750.231403] R13: 0000000010624dd3 R14: 0000000000000001 R15: ffff88020f4eb928
[ 750.231423] FS: 000000000000000
[ 750.231446] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 750.231462] CR2: 00007fff4ea6c418 CR3: 0000000001a03000 CR4: 00000000000406f0
[ 750.231482] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 750.231502] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 750.231522] Process kworker/u:0 (pid: 5, threadinfo ffff88020f4ea000, task ffff88020f4cdb00)
[ 750.231545] Stack:
[ 750.231551] 0000000000000282 ffff88020f4eb900 ffff88020f4eb8c0 ffffffff81075885
[ 750.231574] ffff88020f4ebfd8 ffff88020b388000 ffff88020f4eb92c ffff88020b388018
[ 750.231597] ffff88020f4eb924 ffff88020f4eb928 ffff88020f4eb960 ffffffffa00ddf55
[ 750.231619] Call Trace:
[ 750.231631] [<ffffffff81075
[ 750.231653] [<ffffffffa00dd
[ 750.231677] [<ffffffffa00db
[ 750.231701] [<ffffffffa00e4
[ 750.231725] [<ffffffffa00e5
[ 750.231746] [<ffffffffa009d
[ 750.231772] [<ffffffffa009d
[ 750.231801] [<ffffffffa0053
[ 750.231822] [<ffffffffa00b5
[ 750.231842] [<ffffffffa00b9
[ 750.231865] [<ffffffffa00ba
[ 750.231885] [<ffffffff81081
[ 750.231903] [<ffffffff81082
[ 750.231920] [<ffffffff81081
[ 750.231936] [<ffffffff81086
[ 750.231951] [<ffffffff8100c
[ 750.231969] [<ffffffff81086
[ 750.231984] [<ffffffff8100c
[ 750.232000] Code: e8 4c 8b 75 f0 4c 8b 7d f8 c9 c3 0f 1f 84 00 00 00 00 00 69 c1 e8 03 00 00 49 63 da 41 bd d3 4d 62 10 41 0f af f0 89 c2 c1 fa 1f <41> f7 f9 31 d2 48 63 c8 48 89 d8 48 f7 f1 48 b9 cf f7 53 e3 a5
[ 750.232092] RIP [<ffffffffa00dc
[ 750.232116] RSP <ffff88020f4eb870>
ACTHD: 0xffffffff
EIR: 0x00000000
EMR: 0xffffffff
ESR: 0x00000000
PGTBL_ER: 0x00000000
IPEHR: 0x680b0000
IPEIR: 0x00000000
INSTDONE1: 0xfffffffe
INSTDONE2: 0xffffffff
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
Chipset: sandybridge
CompizPlugins: No value set for `/apps/
CompositorRunning: None
DRM.card0.DP.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.DP.2:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.HDMI.A.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.HDMI.A.2:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.VGA.1:
status: connected
enabled: enabled
dpms: On
modes: 1920x1080 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
edid-base64: AP/////
Date: Mon Feb 14 14:51:37 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
DumpSignature: 803644b9 (IPEHR: 0x680b0000)
ExecutablePath: /usr/share/
GraphicsCard: Subsystem: Intel Corporation Device [8086:2002]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110121)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
ProcKernelCmdLine_: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6~3ubuntu4
libdrm2 2.4.23-1ubuntu3
xserver-
Renderer: Hardware acceleration
SourcePackage: xserver-
Title: [sandybridge] GPU lockup 803644b9 (IPEHR: 0x680b0000)
UserGroups:
dmi.bios.date: 10/25/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.
dmi.board.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-202
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
version.compiz: compiz 1:0.9.2.
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.
version.
version.
version.
version.
summary: |
- [sandybridge] GPU lockup 803644b9 (IPEHR: 0x680b0000) + [sandybridge] GPU lockup (IPEHR: 0x680b0000) |
description: | updated |
description: | updated |
tags: | added: kj-triage |
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | In Progress → Fix Released |
Thank you for following up with a new bug report.
This apport capture is a lot more detailed than bug 715122; in fact with that bug it's not really evident what went wrong (the error codes are all 0's). But this one shows that there's been a divide error. There is no reason not to think it's the same as the previous lockup, so I'm duping the previous one to this one.
Since it sounds like you experience this crash multiple times, can you speculate what actions or activities seem to trigger it the most? A divide-by-zero error seems like something which would have a way to trigger it.