SRU: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Release Notes for Ubuntu |
Undecided
|
Unassigned | ||
| | xf86-video-intel |
Fix Released
|
High
|
||
| | linux (Ubuntu) |
Undecided
|
Unassigned | ||
| | Natty |
Undecided
|
Unassigned | ||
| | Oneiric |
Undecided
|
Unassigned | ||
| | xserver-xorg-video-intel (Ubuntu) |
High
|
Bryce Harrington | ||
| | Natty |
High
|
Bryce Harrington | ||
| | Oneiric |
High
|
Bryce Harrington | ||
Bug Description
[Impact]
Severe GPU lockup affecting the i915/i945 family of Intel chips, resulting in unrecoverable freeze of graphics, black screen and/or corruption, requiring a hard reboot to reset. The issue is widespread amongst these cards as evidenced by the large number of dupes; the hardware is common. Most users report this is a regression in behavior from maverick.
[Background]
Subsequent to the code included in maverick, upstream introduced an optimization to relax fencing on Intel hardware. This change reduced the amount of memory allocated for video buffers. However on older (pre-G33) hardware such as i915/i945 this results in increased chances of GPU lockups.
[Fix for Development Version]
Upstream has opted to disable the relaxed fencing optimization for their driver release, and the change is still present in their active upstream git tree. Thus, we will be pulling this fix when we update X in oneiric.
[Fix for Stable Version]
For natty, the attached patch is a backport of the patch that went upstream. This patch makes relaxed fencing into an xorg.conf option that can be set, and makes it disabled by default for gen < 33 chipsets.
[Steps to Reproduce]
The freezes typically occur intermittently after some period of use. For some people it occurs right at boot, others after minutes or hours of usage. Some users find that certain activities such as web browsing makes the issue more likely to occur, but others do not find it correlated to any particular action.
However, in all cases once the system is frozen, the file /sys/kernel/
With this patch applied, gpu freezes should either go away entirely, or become much less frequent. Freezes which still occur but have IPEHR values outside these two ranges may be unrelated bugs.
[Regression Potential]
The patch itself is relatively small and unlikely to introduce regression.
However, this switches optimization paths within the driver. It restores us to an older codepath so presumably this will at least be as stable as maverick, however the amount of testing this path has received on natty is limited. The code is upstream and being tested by the wider community and so far has not proven problematic.
Because it is disabling an optimization, it is possible some users of older hardware may see performance regress, but should be no worse than what was available in maverick.
[Original Report]
As instructed by Bryce I installed the following kernel on my Asus eee pc 701 running natty:
" Please test with the following kernel:
http://
by doing sudo dpkg -i linux-image....deb
Then I ran update manager.
After rebooting I browsed with google chrome. The system froze after 5 minutes.
I rebooted the same kernel and immediately got this problem popup. In addition there is font corruption - part of the letter t is missing in the browser.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-
Uname: Linux 2.6.38-999-generic i686
Architecture: i386
Chipset: i915gm
CompizPlugins: No value set for `/apps/
CompositorRunning: None
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 800x480
edid-base64:
DRM.card0.VGA.1:
status: connected
enabled: enabled
dpms: On
modes: 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
edid-base64: AP/////
Date: Wed Mar 2 15:23:13 2011
DistUpgraded: Yes, recently upgraded Log time: 2011-02-17 19:00:58.983764
DistroCodename: natty
DistroVariant: ubuntu
DumpSignature: c38b9ae8 (ESR: 0x00000001 IPEHR: 0x02000004)
ExecutablePath: /usr/share/
GraphicsCard:
Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
MachineType: ASUSTeK Computer INC. 701
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
ProcKernelCmdLine_: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6~3ubuntu8
libdrm2 2.4.23-1ubuntu3
xserver-
Renderer: Unknown
SourcePackage: xserver-
Title: [i915gm] GPU lockup c38b9ae8 (ESR: 0x00000001 IPEHR: 0x02000004)
UpgradeStatus: Upgraded to natty on 2011-02-24 (5 days ago)
UserGroups:
dmi.bios.date: 05/04/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1001
dmi.board.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 701
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.4-0ubuntu3
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.
version.
version.
version.
version.
[lspci]
Nux: lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (r
Related branches
Created attachment 43065
i915_error_
Created attachment 43066
BootDmesg.txt
Created attachment 43067
CurrentDmesg.txt
Created attachment 43068
XorgLog.txt
Created attachment 43069
XorgLogOld.txt
This bugzilla won't let me attach the gpu dump, but here's a permalink to it:
|
|
#61 |
*** Bug 34015 has been marked as a duplicate of this bug. ***
|
|
#62 |
This patch would confirm my hypothesis that is an invalid unfenced alignment:
diff --git a/drivers/
index f136899..c970b81 100644
--- a/drivers/
+++ b/drivers/
@@ -1416,6 +1416,7 @@ i915_gem_
+ return i915_gem_
/*
* Older chips need unfenced tiled buffers to be aligned to the left
* edge of an even tile row (where tile rows are counted as if the bo is
We packaged this patch into a kernel for the bug reporter to test:
http://
We have not yet heard back from him in a couple weeks.
However, we asked other bug reporters with vaguely similar lockups to test as well, and this past weekend one of them tested it and provided the following dmesg after reproducing a lockup.
| summary: |
- [i915gm] GPU lockup c38b9ae8 (ESR: 0x00000001 IPEHR: 0x02000004) + [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) |
David Coggins - I've forwarded this bug upstream to http://
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in xserver-xorg-video-intel: | |
| importance: | Unknown → Critical |
| status: | Unknown → Confirmed |
Hmm, I think I'm seeing this too on my X41T:
Recently upgraded Debian and kernel and got gpu hangs again.
I upgraded to latest libdrm2 and xf86-video-intel, but still getting gpu hangs.
Especially chrome seems to have a knack for causing these (aggressive use of acceleration features I guess).
Linux navi 2.6.38-rc7 #64 PREEMPT Sun Mar 6 14:32:50 CET 2011 i686 GNU/Linux
ii libdrm2 2.4.24-1 Userspace interface to kernel DRM services -
ii xserver-xorg-v 2:2.14.901-1 X.Org X server -- Intel i8xx, i9xx display d
(Both built myself from newest upstream packages released last week).
intel_gpu_dump:
ACTHD: 0xffffffff
EIR: 0x00000000
EMR: 0xffffffed
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x02000004
IPEIR: 0x00000000
INSTDONE: 0x038ff8c1
busy: IDCT
busy: IQ
busy: PR
busy: VLD
busy: Instruction parser
busy: Setup engine
busy: Windowizer
busy: Intermediate Z
busy: Bypass FIFO
busy: Pixel shader
busy: Color calculator
Ringbuffer: Reminder: head pointer is GPU read, tail pointer is CPU write
ringbuffer at 0x00000000:
(copy&paste from terminal, forgot to redirect into file before resetting the gpu with a suspend-resume cycle).
dmesg:
[29103.032023] [drm:i915_
[29103.032023] [drm:i915_
[29103.032023] [drm:i915_reset] *ERROR* Failed to reset chip.
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.0 0300: 8086:2592 (rev 03)
00:02.1 0380: 8086:2792 (rev 03)
Vendor: 0x8086, Device: 0x2592, Revision: 0x03 (B1/C0)
BTW, while a suspend-resume should reset the gpu, I see this:
[31055.564022] [drm] Manually setting wedged to 0
[31055.564022] [drm:i915_reset] *ERROR* Failed to reset chip.
Why does it fail?
The units are not busy anymore according to intel_gpu_top, so I'd expect "echo 0 > /sys/kernel/
Created attachment 44183
i915 dump after s2mem (tried to recover from wedged gpu), but i915 claims it still can't reset the gpu
|
|
#67 |
(In reply to comment #11)
> BTW, while a suspend-resume should reset the gpu, I see this:
>
> [31055.564022] [drm] Manually setting wedged to 0
> [31055.564022] [drm:i915_reset] *ERROR* Failed to reset chip.
> Why does it fail?
It fails because we have not found the means to successfully reset that chipset yet. It may well be the only way is to power cycle the PCI device. Meh.
> The units are not busy anymore according to intel_gpu_top, so I'd expect "echo
> 0 > /sys/kernel/
The units are idle because the chip hit a fatal error and disabled those units.
(In reply to comment #13)
> (In reply to comment #11)
> > BTW, while a suspend-resume should reset the gpu, I see this:
> >
> > [31055.564022] [drm] Manually setting wedged to 0
> > [31055.564022] [drm:i915_reset] *ERROR* Failed to reset chip.
> > Why does it fail?
>
> It fails because we have not found the means to successfully reset that chipset
> yet. It may well be the only way is to power cycle the PCI device. Meh.
>
> > The units are not busy anymore according to intel_gpu_top, so I'd expect "echo
> > 0 > /sys/kernel/
>
> The units are idle because the chip hit a fatal error and disabled those units.
I don't think so. They are only idle after coming back out of suspend to ram, so I think it's probably because the GPU was power-cycled.
Both resume from disk and resume from ram have the same effect here.
I think it would be very helpful if KMS/DRM could recover from the GPU hang after suspend to ram or suspend to disk, when the GPU was power-cycled. It used to be the case that 'echo 1 > i915_wedged' would restart the driver after resume, but it seems some internals have changed so that this no longer works. If it would be able to recover in this case it would avoid the need to completely reboot the system to recover.
|
|
#69 |
*** Bug 34948 has been marked as a duplicate of this bug. ***
|
|
#70 |
Created attachment 44468
i915_error_state from #34948
Attaching another i915_error_state variant.
| Changed in xserver-xorg-video-intel: | |
| importance: | Critical → Unknown |
| status: | Confirmed → Unknown |
| Changed in xserver-xorg-video-intel: | |
| importance: | Unknown → High |
| status: | Unknown → Confirmed |
|
|
#71 |
Can you give drm-intel-staging, and in particular,
commit 0faba0d4e493618
Author: Chris Wilson <email address hidden>
Date: Thu Mar 17 15:23:22 2011 +0000
drm/i915: Fix tiling corruption from pipelined fencing
... even though it was disabled. A mistake in the handling of fence reuse
caused us to skip the vital delay of waiting for the object to finish
rendering before changing the register.
Bugzilla: https:/
Cc: Andy Whitcroft <email address hidden>
Cc: Daniel Vetter <email address hidden>
Reviewed-by: Daniel Vetter <email address hidden>
[Note for 2.6.38-stable, we need to reintroduce the interruptible passing]
Signed-off-by: Chris Wilson <email address hidden>
a whirl?
Confirming this on the latest Natty daily build. I logged on and got a message about kernel problem, clicked "report problem", entered my password and got this crash.
Also, the system froze on the previous boot. The kernel was still responsive, I managed to get a proper shutdown, but X and even the keyboard NumPad toggling didn't work.
The system froze for me testing the latest natty 2.6.38-7.36 which should incorporate the fix for bug 717114
drm/i915: Fix tiling corruption from pipelined fencing
Mar 21 11:29:13 eee kernel: [ 0.000000] Linux version 2.6.38-7-generic (buildd@roseapple) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4) ) #36-Ubuntu SMP Fri Mar 18 22:05:25 UTC 2011 (Ubuntu 2.6.38-7.36-generic 2.6.38)
Mar 21 11:47:30 eee kernel: [ 1115.992048] [drm:i915_
Mar 21 11:47:30 eee kernel: [ 1115.998408] [drm:i915_
Apport is not generating a problem popup when I next reboot at the moment.
A small amount of testing with the terminal does not show any corruption which I was seeing 2 weeks ago bug 717114
|
|
#72 |
Working on the theory that it is one and the same bug:
commit b5b5ac2dec49ea5
Author: Chris Wilson <email address hidden>
Date: Thu Mar 17 15:23:22 2011 +0000
drm/i915: Fix tiling corruption from pipelined fencing
... even though it was disabled. A mistake in the handling of fence reuse
caused us to skip the vital delay of waiting for the object to finish
rendering before changing the register.
Bugzilla: https:/
Cc: Andy Whitcroft <email address hidden>
Cc: Daniel Vetter <email address hidden>
Reviewed-by: Daniel Vetter <email address hidden>
[Note for 2.6.38-stable, we need to reintroduce the interruptible passing]
Signed-off-by: Chris Wilson <email address hidden>
Tested-by: Dave Airlie <email address hidden>
| Changed in xserver-xorg-video-intel: | |
| status: | Confirmed → Fix Released |
Original reporter tested a kernel that includes commit b5b5ac2d patched in and says he still sees the hang:
David Coggins wrote on 2011-03-20:
The system froze for me testing the latest natty 2.6.38-7.36 which should incorporate the fix for bug 717114
drm/i915: Fix tiling corruption from pipelined fencing
Mar 21 11:29:13 eee kernel: [ 0.000000] Linux version 2.6.38-7-generic (buildd@roseapple) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4) ) #36-Ubuntu SMP Fri Mar 18 22:05:25 UTC 2011 (Ubuntu 2.6.38-7.36-generic 2.6.38)
Mar 21 11:47:30 eee kernel: [ 1115.992048] [drm:i915_
Mar 21 11:47:30 eee kernel: [ 1115.998408] [drm:i915_
Apport is not generating a problem popup when I next reboot at the moment.
A small amount of testing with the terminal does not show any corruption which I was seeing 2 weeks ago bug 717114
| Bryce Harrington (bryce) wrote : | #6 |
Hi David, thanks for the feedback, sorry to hear it didn't solve it.
I've reopened the upstream bug report and included your comment. It would be very helpful if you could add yourself to the CC of the upstream bug report, so you can spot and respond to upstream's suggestions for things to test.
|
|
#74 |
*** Bug 35608 has been marked as a duplicate of this bug. ***
|
|
#75 |
Created attachment 44880
i915_error_state from #35608
|
|
#76 |
*** Bug 35647 has been marked as a duplicate of this bug. ***
|
|
#77 |
Created attachment 44881
i915_error_state from #35647
| Changed in xserver-xorg-video-intel: | |
| status: | Fix Released → Confirmed |
| mkis62 (mihaikx62) wrote : | #7 |
Still crashing. It happens on rapid mouse movement or scroll in Firefox.
2.6.38-7 worked fine for few days...
Reported on 2011-04-01 as Bug #747676, got the reply 'This bug has been marked a duplicate of bug 727594', so here we are
|
|
#78 |
*** Bug 36000 has been marked as a duplicate of this bug. ***
|
|
#79 |
Created attachment 45335
i915_error_state from #36000
| Teun (teunkloosterman) wrote : | #8 |
Again, this is not a critical bug for me.
I filed three reports in this bug which all happened when the crash reporter was reporting another bug. The crash reporter crashes and confronts me with this bug.
My computer doesn't stall or in any other way starts behaving badly, it's only when a diagnostic report on another application is being created that the bug reporter crashes.
System froze testing natty 2.6.38-8.41. I would be interested to know whether this kernel contains the Mar 25 patch
drm/i915: Round-up GTT allocations for unfenced surfaces to the next tile row ?
Alternatively does the daily mainline kernel 2.6.39-999 contain the patch?
| Jim Bronson (jim-bronson) wrote : Re: [Bug 727594] Re: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) | #10 |
I gave up and went back to 10.04 LTS. I don't like Unity anyway.
Unsubscribe
On Fri, Apr 8, 2011 at 4:45 AM, David Coggins <email address hidden> wrote:
> System froze testing natty 2.6.38-8.41. I would be interested to know
> whether this kernel contains the Mar 25 patch
>
> drm/i915: Round-up GTT allocations for unfenced surfaces to the next
> tile row ?
>
> Alternatively does the daily mainline kernel 2.6.39-999 contain the
> patch?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (747676).
> https:/
>
> Title:
> [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004)
>
> Status in X.org xf86-video-intel:
> Confirmed
> Status in “linux” package in Ubuntu:
> New
> Status in “xserver-
> Triaged
>
> Bug description:
> Binary package hint: xserver-
>
> As instructed by Bryce I installed the following kernel on my Asus eee pc 701 running natty:
> " Please test with the following kernel:
>
> http://
>
> by doing sudo dpkg -i linux-image....deb
>
> Then I ran update manager.
>
> After rebooting I browsed with google chrome. The system froze after 5
> minutes.
>
> I rebooted the same kernel and immediately got this problem popup. In
> addition there is font corruption - part of the letter t is missing in
> the browser.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: xserver-
> Uname: Linux 2.6.38-999-generic i686
> Architecture: i386
> Chipset: i915gm
> CompizPlugins: No value set for `/apps/
> CompositorRunning: None
> DRM.card0.LVDS.1:
> status: connected
> enabled: enabled
> dpms: On
> modes: 800x480
> edid-base64:
> DRM.card0.VGA.1:
> status: connected
> enabled: enabled
> dpms: On
> modes: 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
> edid-base64: AP/////
> Date: Wed Mar 2 15:23:13 2011
> DistUpgraded: Yes, recently upgraded Log time: 2011-02-17 19:00:58.983764
> DistroCodename: natty
> DistroVariant: ubuntu
> DumpSignature: c38b9ae8 (ESR: 0x00000001 IPEHR: 0x02000004)
> ExecutablePath: /usr/share/
> GraphicsCard:
> Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
> Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
> InterpreterPath: /usr/bin/python2.7
> MachineType: ASUSTeK Computer INC. 701
> ProcCmdline: /usr/bin/python /usr/share/
> ProcEnviron:
>
> ProcKernelCmdLine: BOOT_IMAGE=
I suspect that this bug is related to Bug 36147
Test if reverting commit cc930a37612341a
helps
|
|
#81 |
Bryce, I'm confident that Knut identified the same issue and so disabling relaxed-fencing for the release should fix these as well. (I have lingering doubts since we tried the obvious kernel workarounds, but then again I think we may have a fundamental bug in our allocation ala gen2.) Obviously, if I am wrong, let's open the bug again.
commit 686018f283f1d13
Author: Chris Wilson <email address hidden>
Date: Tue Apr 12 08:23:04 2011 +0100
Turn relaxed-fencing off by default for older (pre-G33) chipsets
There are still too many unresolved bugs, typically GPU hangs, that are
related to using relaxed fencing (i.e. only allocating the minimal
amount of memory required for a buffer) on older hardware, so turn off
the feature by default for the release.
Reported-
Bugzilla: https:/
Signed-off-by: Chris Wilson <email address hidden>
Acked-by: Daniel Vetter <email address hidden>
I can't look too deeply into it right now but it looks like this hasn't fixed it for me. The xf86-video-intel I built definitely included that commit and I was running 2.6.38.2.
| Changed in xserver-xorg-video-intel: | |
| status: | Confirmed → Fix Released |
Is there anyone who can help to release a bug fixed package for Natty? My laptop crashed almost every day and every boot up. I have to remote login (ssh) to my laptop, kill X and restart my GUI every time.
Why should I use a Natty beta version? Because it seems only Natty's graphics chip-set driver support my Sandy Bridge GPU, ( VESA is too slow for me, even I don't need compiz and any 3D effect ),
Thank you.
| Bryce Harrington (bryce) wrote : | #12 |
I backported the patch from upstream that they believe will resolve this issue. It might be too late to include this in natty, however if people test it quickly and if it is found to eliminate the freezes on i915 maybe there's a chance.
My backport patch is available in my PPA here: https:/
If you test it and find it resolves the issue sufficiently let me know.
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| status: | Triaged → Incomplete |
| mkis62 (mihaikx62) wrote : | #13 |
Installed the patch from PPA
Still crashing -- scrolling on a page in Firefox with flash-video content freezes all.
The problem cannot be reported (not genuine Ubuntu package)
| Colin (colinnc) wrote : | #14 |
The PPA patch seems to have fixed the problem for me. Using Google Chrome would cause a lockup within five minutes before, so far no lockups after one hour of use. I'll update if anything changes.
Thanks!
| Robin.He (hechu) wrote : | #16 |
Hi, unfortunately, the PPA patch did not fix the problem for me.
I am running Firefox, LibreOffice, gnome-terminal, gedit and a third part IM software, when I am typing in the gnome-terminal, the X locked, I have to force power off my laptop (by push the power button) because I don't have another computer to remote login this time.
Now I set "fbdev" as my GPU driver. It runs OK except the speed.
For my case, please refer to:
https:/
| Bryce Harrington (bryce) wrote : | #17 |
@Robin, hmm, looks like your bug got mistakenly duped to this one. You have a sandybridge system, whereas near as we can tell this bug is specific to the i915/i945 architecture. I'll undupe your bug report.
That leaves us with one yes, one no... can anyone else provide feedback? I'd like to see a few yes's (and more yes's than no's) before proceeding with this fix.
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| status: | Incomplete → New |
| status: | New → Incomplete |
| Eric Appleman (erappleman) wrote : | #18 |
I'm not seeing this on i945gm with the final freeze kernel.
| mkis62 (mihaikx62) wrote : | #19 |
Bryce, this time I booted on 2.6.38-8 with your patch from PPA. Seems to be OK, even after some 'stressing' in Firefox (multiple tabs, video, scrolling...).
Thanks!
My eeepc is running ok after installing the backport from the fig ppa. I used the system for several hours last night in google chrome and again this morning. Previously the bug could take all day to show up. Scrolling is a little laggy. However this evening I am seeing slight font corruption in the letter p in the console and gedit.
| Eakan Gopalakrishnan (eakangk) wrote : Re: [Bug 727594] Re: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) | #21 |
i always keep getting the fonts displayed weirdly..sometimes the upper part
of 't' is invisible, other times the lower part of letters like 'p' is
invisible. Sometimes strange weird lines appear.
wonder what wrong.
On Thu, Apr 21, 2011 at 12:10 PM, David Coggins
<email address hidden>wrote:
> My eeepc is running ok after installing the backport from the fig ppa. I
> used the system for several hours last night in google chrome and again
> this morning. Previously the bug could take all day to show up.
> Scrolling is a little laggy. However this evening I am seeing slight
> font corruption in the letter p in the console and gedit.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004)
>
> Status in X.org xf86-video-intel:
> Fix Released
> Status in “linux” package in Ubuntu:
> New
> Status in “xserver-
> Incomplete
>
> Bug description:
> Binary package hint: xserver-
>
> As instructed by Bryce I installed the following kernel on my Asus eee pc
> 701 running natty:
> " Please test with the following kernel:
>
> http://
>
> by doing sudo dpkg -i linux-image....deb
>
> Then I ran update manager.
>
> After rebooting I browsed with google chrome. The system froze after 5
> minutes.
>
> I rebooted the same kernel and immediately got this problem popup. In
> addition there is font corruption - part of the letter t is missing in
> the browser.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: xserver-
> Uname: Linux 2.6.38-999-generic i686
> Architecture: i386
> Chipset: i915gm
> CompizPlugins: No value set for
> `/apps/
> CompositorRunning: None
> DRM.card0.LVDS.1:
> status: connected
> enabled: enabled
> dpms: On
> modes: 800x480
> edid-base64:
> DRM.card0.VGA.1:
> status: connected
> enabled: enabled
> dpms: On
> modes: 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768
> 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480
> 640x480 720x400
> edid-base64:
> AP/////
> Date: Wed Mar 2 15:23:13 2011
> DistUpgraded: Yes, recently upgraded Log time: 2011-02-17 19:00:58.983764
> DistroCodename: natty
> DistroVariant: ubuntu
> DumpSignature: c38b9ae8 (ESR: 0x00000001 IPEHR: 0x02000004)
> ExecutablePath: /usr/share/
> GraphicsCard:
> Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
> [8086:2592] (rev 04) (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
> Subsystem: ASUSTeK Computer Inc. Device [1043:82d9]
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
> InterpreterPath: /usr/bin/python2.7
> MachineType: ASUSTeK Computer INC. 7...
Lets leave the font corruption to a different bug, unless it can be definitively shown to be caused by the fig ppa.
So, one more yes vote from mkis62, and perhaps too early to say for David.
| John T. Folden (john-t-folden) wrote : | #23 |
I think the fig ppa has fixed the issue for me...
| Bryce Harrington (bryce) wrote : | #24 |
Alright I've gotten a few more confirmations of the fix on bugs #755693 and #763259. I think we may be too late for the release unfortunately, but I can try to get it accepted as an SRU. The criteria for SRUs are stricter than development changes though. The more +1 confirmations we can gather that this change resolves freeze issues the better.
Since this bug report is the oldest of this family of bugs I'm going to make it the master for all the dupes and the primary for filing the SRU. Apologies ahead of time if this generates a lot of email traffic for everyone (you can unsub via the bug report in launchpad if you don't want the emails, but hopefully it should be over and done in a couple weeks).
@David, since you're the original reporter on this bug report, would you mind following up with your latest findings vis a vis the ppa fix?
| Changed in xserver-xorg-video-intel (Ubuntu): | |
| status: | Incomplete → In Progress |
| description: | updated |
| Bryce Harrington (bryce) wrote : | #25 |
Fix confirmations on dupe bugs:
https:/
https:/
https:/
https:/
https:/
| Changed in xserver-xorg-video-intel (Ubuntu Natty): | |
| milestone: | none → natty-updates |
| Changed in linux (Ubuntu Natty): | |
| status: | New → Invalid |
| Changed in xserver-xorg-video-intel (Ubuntu Natty): | |
| assignee: | nobody → Bryce Harrington (bryce) |
| summary: |
- [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) + SRU: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) |
| Changed in xserver-xorg-video-intel (Ubuntu Natty): | |
| status: | In Progress → Fix Committed |
| AJenbo (ajenbo) wrote : | #26 |
I really hope this makes it in the release, I was not even able to login prior to installing the fix via the terminal in recovery mode :(
| Bryce Harrington (bryce) wrote : | #27 |
| AJenbo (ajenbo) wrote : | #28 |
Bryce, the patch is empty...
The freezes have not occurred for several days now so I would consider them fixed. The patch has not made other problems worse.
| Christian Göbel (christiangoebel) wrote : | #30 |
+1
I tested the ppa. Everything looks good so far - no crash since I installed the patched driver.
| Bryce Harrington (bryce) wrote : | #31 |
> Bryce, the patch is empty...
Ha, true enough. Let's try that again.
Btw, I'm pretty sure the release is already more or less in the bag, so the fix is not likely to make it to the cd. (I could be wrong; it's a severe enough bug the archive team might pull it in if there are other last minute bugs making it worthwhile to regenerate the CD iso.)
It's more likely this will go through the SRU process. That means, it'll be reviewed and approved to go into natty-proposed for people to test, where it'll love for a period from a week to several weeks until enough testing has been done to show it does not cause regression. At that point it will move to natty-updates and be generally available to all users.
If a lot of people test -proposed and give it a +1, that will help accelerate getting the fix into the release. If people test it and find any regressions, that will significantly delay it going in until those issues can be investigated and resolved. So, hopefully lots of people give +1's and no one gives -1's, and we'll see this live for natty for people to update to post-release.
| AJenbo (ajenbo) wrote : | #32 |
With some system not even able to boot normally that wouldn't be very user friendly.
It's looking more and more like Lucid and i8xx all over again :(
Reopening, though I'm not sure if Cuirot is the reporter.
Chris, if it does fix, I'd suggest marking dup as resolution.
If we're going to use surnames, it's Le Cuirot please!
I'm not the reporter and I'm not 100% sure that my issue is the same but it is very telling that all these similar bug reports sprung up around the same time.
I would do a bisect but it's my wife's laptop and I haven't found a quick way to reproduce the issue. It usually occurs around 15 minutes into using Chromium. If someone could suggest a reliable way to reproduce it (like a GPU stress tester?) then I'll give it a try.
Accepted xserver-
| tags: | added: verification-needed |
| Changed in xserver-xorg-video-intel: | |
| status: | Fix Released → Confirmed |
| description: | updated |
I installed the package from natty proposed replacing the fig package yesterday and since then there have been no freezes.
| AJenbo (ajenbo) wrote : | #35 |
This issue should probably be mentioned in the release notes.
| Bryce Harrington (bryce) wrote : Re: [Bug 727594] Re: SRU: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004) | #36 |
On Thu, Apr 28, 2011 at 03:32:06AM -0000, AJenbo wrote:
> This issue should probably be mentioned in the release notes.
It is; I added it there earlier today.
| tags: |
added: verification-done removed: verification-needed |
| mic (mic-launchpad) wrote : | #37 |
I am using the package xserver-
What package would that be?
On Wed, Apr 27, 2011 at 9:14 PM, David Coggins <email address hidden>wrote:
> I installed the package from natty proposed replacing the fig package
> yesterday and since then there have been no freezes.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (769862).
> https:/
>
> Title:
> SRU: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004)
>
> Status in X.org xf86-video-intel:
> Confirmed
> Status in “linux” package in Ubuntu:
> Invalid
> Status in “xserver-
> Fix Committed
> Status in “linux” source package in Natty:
> Invalid
> Status in “xserver-
> Fix Committed
>
> Bug description:
> [Impact]
> Severe GPU lockup affecting the i915/i945 family of Intel chips, resulting
> in unrecoverable freeze of graphics, black screen and/or corruption,
> requiring a hard reboot to reset. The issue is widespread amongst these
> cards as evidenced by the large number of dupes; the hardware is common.
> Most users report this is a regression in behavior from maverick.
>
> [Background]
> Subsequent to the code included in maverick, upstream introduced an
> optimization to relax fencing on Intel hardware. This change reduced the
> amount of memory allocated for video buffers. However on older (pre-G33)
> hardware such as i915/i945 this results in increased chances of GPU lockups.
>
> [Fix for Development Version]
> Upstream has opted to disable the relaxed fencing optimization for their
> driver release, and the change is still present in their active upstream git
> tree. Thus, we will be pulling this fix when we update X in oneiric.
>
> [Fix for Stable Version]
> For natty, the attached patch is a backport of the patch that went
> upstream. This patch makes relaxed fencing into an xorg.conf option that
> can be set, and makes it disabled by default for gen < 33 chipsets.
>
> [Steps to Reproduce]
> The freezes typically occur intermittently after some period of use. For
> some people it occurs right at boot, others after minutes or hours of usage.
> Some users find that certain activities such as web browsing makes the
> issue more likely to occur, but others do not find it correlated to any
> particular action.
>
> However, in all cases once the system is frozen, the file
> /sys/kernel/
> for the IPEHR value. The exact value appears to vary greatly from hw
> to hw, but common values tend to be either in the 0x02xxxxxx or
> 0x7xxxxxxx range.
>
> With this patch applied, gpu freezes should either go away entirely,
> or become much less frequent. Freezes which still occur but have
> IPEHR values outside these two ranges may be unrelated bugs.
>
> [Regression Potential]
> The patch itself is relatively small and unlikely to introduce regression.
>
> However, this switches optimization paths within the driver. It
> restores us to an older codepath so presumably this will at least be
> as stable as maverick, however the amount of testing this path has
> received on natty i...
| Patrick M (prmillius) wrote : | #39 |
My machine boots into a blank screen, except the times it gives me the option to boot into recovery mode at boot up. Then if I run failsafex graphic from the menu I get a decent GUI. Maybe the answer is to just have a way to always boot in failsafe mode.
| Bryce Harrington (bryce) wrote : | #40 |
On Sun, May 01, 2011 at 03:15:29AM -0000, mic wrote:
> I am using the package xserver-
> several days, freezes are less frequent. It is better than before, unity
> is able (sometimes) to run for several hours. Still I have to reboot
> machine several times a day.
You could have another bug at work (we've seen this before), or an
underlying condition that exacerbates the problem.
What this fix does is increase the size of the memory pool the gpu uses.
It's sort of like instead of requiring it to hit the bullseye on a
target we're just asking that it hit anywhere on the target or the hay
bales behind it. So whatever causes your GPU to be such a bad shot
still exists, but it's not getting kicked out of the competition so
much.
In general, the two things needed for GPU bug reports are the 'dmesg'
and /sys/kernel/
especially, as that seems to be a roughly good indicator of dupes. If
it's still the same values as this bug (0x02xxxxxx or 0x7xxxxxxx) then
your system may just be sensitive. If it's a very different value, then
might be worth handling it as a second, unrelated bug and handling it
separately.
| Bryce Harrington (bryce) wrote : | #41 |
On Sun, May 01, 2011 at 01:00:49PM -0000, Jamison Lofthouse wrote:
> What package would that be?
xserver-
(It's essentially the same as the fig ppa, just different version number
and changelog entry.)
| Bryce Harrington (bryce) wrote : | #42 |
On Sun, May 01, 2011 at 06:04:06PM -0000, Patrick M wrote:
> My machine boots into a blank screen, except the times it gives me the
> option to boot into recovery mode at boot up.
Heh, you have to explain a lot more than that. Did the issue only occur
after installing the fix? Do you have GPU lockups matching this bug
prior to the black screen? Or do you see GPU error codes matching this
bug when it is black screened? What is your graphics card?
In general, I would suggest to all, unless you KNOW you have this exact
bug, or if you have found a regression which is traceable specifically
to this fix, let's handle your issue on separate bug reports, not here.
That should help spare people from lots of extraneous email...
> Then if I run failsafex
> graphic from the menu I get a decent GUI. Maybe the answer is to just
> have a way to always boot in failsafe mode.
It's not a bad idea. I've filed this as bug #775093, feel free to
subscribe if you'd like to follow it. I plan on spending some time
reworking X diagnostic tools during oneiric, and this would fit with
those plans.
| Launchpad Janitor (janitor) wrote : | #43 |
This bug was fixed in the package xserver-
---------------
xserver-
* Add 119_disable_
optimization is suspected as the cause for various i915/945 gpu lockup
issues. This disables the optimization by default but adds an
xorg.conf parameter to let people experiment with it turned on.
(LP: #727594, #761143, #761632, #755693)
-- Bryce Harrington <email address hidden> Fri, 22 Apr 2011 19:12:55 -0700
| Changed in xserver-xorg-video-intel (Ubuntu Natty): | |
| status: | Fix Committed → Fix Released |
| Martin Pitt (pitti) wrote : | #44 |
Copied to oneiric as well.
| Changed in xserver-xorg-video-intel (Ubuntu Oneiric): | |
| milestone: | natty-updates → none |
| status: | Fix Committed → Fix Released |
Has this happened in the released version (released recently) not in the
beta2 version?
On Mon, May 2, 2011 at 8:53 AM, Martin Pitt <email address hidden> wrote:
> Copied to oneiric as well.
>
> ** Changed in: xserver-
> Status: Fix Committed => Fix Released
>
> ** Changed in: xserver-
> Milestone: natty-updates => None
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (769862).
> https:/
>
> Title:
> SRU: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000004)
>
> Status in Release Notes for Ubuntu:
> New
> Status in X.org xf86-video-intel:
> Confirmed
> Status in “linux” package in Ubuntu:
> Invalid
> Status in “xserver-
> Fix Released
> Status in “linux” source package in Natty:
> Invalid
> Status in “xserver-
> Fix Released
> Status in “linux” source package in Oneiric:
> Invalid
> Status in “xserver-
> Fix Released
>
> Bug description:
> [Impact]
> Severe GPU lockup affecting the i915/i945 family of Intel chips, resulting
> in unrecoverable freeze of graphics, black screen and/or corruption,
> requiring a hard reboot to reset. The issue is widespread amongst these
> cards as evidenced by the large number of dupes; the hardware is common.
> Most users report this is a regression in behavior from maverick.
>
> [Background]
> Subsequent to the code included in maverick, upstream introduced an
> optimization to relax fencing on Intel hardware. This change reduced the
> amount of memory allocated for video buffers. However on older (pre-G33)
> hardware such as i915/i945 this results in increased chances of GPU lockups.
>
> [Fix for Development Version]
> Upstream has opted to disable the relaxed fencing optimization for their
> driver release, and the change is still present in their active upstream git
> tree. Thus, we will be pulling this fix when we update X in oneiric.
>
> [Fix for Stable Version]
> For natty, the attached patch is a backport of the patch that went
> upstream. This patch makes relaxed fencing into an xorg.conf option that
> can be set, and makes it disabled by default for gen < 33 chipsets.
>
> [Steps to Reproduce]
> The freezes typically occur intermittently after some period of use. For
> some people it occurs right at boot, others after minutes or hours of usage.
> Some users find that certain activities such as web browsing makes the
> issue more likely to occur, but others do not find it correlated to any
> particular action.
>
> However, in all cases once the system is frozen, the file
> /sys/kernel/
> for the IPEHR value. The exact value appears to vary greatly from hw
> to hw, but common values tend to be either in the 0x02xxxxxx or
> 0x7xxxxxxx range.
>
> With this patch applied, gpu freezes should either go away entirely,
> or become much less frequent. Freezes which still occur but have
> IPEHR values outside these two ranges may be unrelated...
| jtl999 (jtl999) wrote : | #46 |
Ithink this is related to my Minecraft bug on dh55hc mobo
| Richard Kleeman (kleeman) wrote : | #47 |
I have the patched version and am still getting freezes in both unity-2d and gnome classic
| Bryce Harrington (bryce) wrote : | #48 |
@Richard, file a new bug report, this SRU is complete.
See:
https:/
https:/
| Jonas Eberle (jonas-eberle) wrote : | #49 |
Confirming that this is fixed on my G915. I had very often lockups with the natty beta's, since 1 week (when this new driver and a new kernel arrived), not even one.
Thanks to all working on this.
Still happening on 2.6.39. :(
| Shriramana Sharma (jamadagni) wrote : | #50 |
Hello, please see bug 768986. It is perhaps what Richard (comment #47) has. As he notes, I also have the patched version *7.1 and I still have freezes, but upon Kubuntu login. (I don't use GNOME so I can't say about that.)
|
|
#86 |
Created attachment 48884
Use full-fence size for alignment on pre-G33
The complication was that there was a second bug that prevented the original patch from preventing the unalignment of the buffers.
|
|
#88 |
commit e28f87116503f79
Author: Chris Wilson <email address hidden>
Date: Mon Jul 18 13:11:49 2011 -0700
drm/i915: Fix unfenced alignment on pre-G33 hardware
Align unfenced buffers on older hardware to the power-of-two object
size. The docs suggest that it should be possible to align only to a
power-of-two tile height, but using the already computed fence size is
easier and always correct. We also have to make sure that we unbind
misaligned buffers upon tiling changes.
In order to prevent a repetition of this bug, we change the interface
to the alignment computation routines to force the caller to provide
the requested alignment and size of the GTT binding rather than assume
the current values on the object.
Reported-
Bugzilla: https:/
Signed-off-by: Chris Wilson <email address hidden>
Cc: <email address hidden>
Reviewed-by: Daniel Vetter <email address hidden>
Signed-off-by: Keith Packard <email address hidden>
| Changed in xserver-xorg-video-intel: | |
| status: | Confirmed → Fix Released |
| david6 (andrew-dowden) wrote : | #51 |
I am dealing with an issue (Bug #882893 ) that may be related.
In general the PC (with Intel 82865G) is running OK, with Ubuntu 11.10 + Unity-2D, and latest updates.
Only problem: GPU (or CPU) crashes at 'screen OFF', on screensaver timeout.
( I will try: RevertingIntelD
| TheShadow (theshadow-shadowpedia) wrote : | #52 |
My coworker and I who are running the same model of machine are experiencing random lock ups. The holy hint is a message in the syslog and kern about the GPU hanging. I've included some data in the attached file.
It started recently for me within the last two weeks, definitely after some round of updates. Which ones I'm not certain of.
| piccobello (piccobello) wrote : | #53 |
I have an old machine with this intel graphics card:
$ lspci -v|grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
I am using Kubuntu natty since a while now, and I never had a problem whatsoever.
I only learned about this bug as I got the scary warning while trying to upgrade to oneiric.
Should I be worried? Is there something useful I can do?
I have arrived to natty via an upgrade, and I always kept all desktop effects deactivated, I guess that may be why I never had any issues.
| Changed in ubuntu-release-notes: | |
| status: | New → Invalid |
Forwarding this bug from Ubuntu reporter mkis62:
http://
[Problem]
GPU lockup (of the "Hangcheck timer elapsed" variety) on 2.6.38-2 kernel and 2.14.0 intel driver with i915gm hardware. No compositor is running.
[Original Description]
X crashed while setting preferences in Decibel Audio Player
tty1-6 works ... rebooting...
From GPU dump:
ACTHD: 0xffffffff
EIR: 0x00000000
EMR: 0xffffffed
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x02000004
IPEIR: 0x00000000
INSTDONE: 0x03c7c081
busy: IDCT
busy: IQ
busy: PR
busy: VLD
busy: Instruction parser
busy: Windowizer
busy: Intermediate Z
busy: Perspective interpolation
busy: Texture decompression
busy: Sampler Cache
busy: Filtering
busy: Bypass FIFO
busy: Pixel shader
busy: Color calculator
busy: Map L2
From dmesg:
[ 2026.252160] [drm:i915_
[ 2026.254795] [drm:i915_
DistroRelease: Ubuntu 11.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.38-2-generic i686
Architecture: i386
Chipset: i915gm
CompisitorRunning: None
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x768
 edid-base64: DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Feb 7 18:50:19 2011
DistUpgraded: Yes, recently upgraded Log time: 2011-01-03 14:04:23.058239
DistroCodename: natty
DistroVariant: ubuntu
DumpSignature: 82856c05
ExecutablePath: /usr/share/
GconfCompiz:
GraphicsCard:
 Subsystem: Acer Incorporated [ALI] Device [1025:006a]
   Subsystem: Acer Incorporated [ALI] Device [1025:006a]
InterpreterPath: /usr/bin/python2.7
MachineType: Acer TravelMate 2410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
ProcKernelCmdLine_: BOOT_IMAGE=
RelatedPackageV
 xserver-xorg 1:7.6~3ubuntu3
 libdrm2 2.4.23-1ubuntu3
 xserver-
Renderer: Hardware acceleration
SourcePackage: xserver-
Title: [i915gm] GPU lockup 82856c05
UserGroups:
dmi.bios.date: 02/07/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.09
dmi.board.name: Morar
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: TravelMate 2410
dmi.product.
d...