[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xf86-video-intel |
Won't Fix
|
Medium
|
|||
linux (Ubuntu) |
Incomplete
|
Low
|
Unassigned | ||
xserver-xorg-video-intel (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked.
WORKAROUND: Edit your /etc/default/grub from:
GRUB_CMDLINE_
to:
GRUB_CMDLINE_
run the following and reboot:
sudo update-grub
The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-
Uname: Linux 3.6.0-rc3-
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Chipset: sandybridge-m-gt2
Date: Sun Aug 26 16:06:32 2012
DistroCodename: quantal
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10
EcryptfsInUse: Yes
ExecutablePath: /usr/share/
GpuHangFrequency: Continuously
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
InterpreterPath: /usr/bin/
MachineType: Dell Inc. Dell System XPS L502X
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu3
libdrm2 2.4.38-0ubuntu2
xserver-
SourcePackage: xserver-
Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/29/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.
Rocko (rockorequin) wrote : | #1 |
- BootDmesg.txt Edit (62.7 KiB, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (10.2 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
- Lspci.txt Edit (34.0 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (707 bytes, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (7.1 KiB, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (4.1 KiB, text/plain; charset="utf-8")
- ProcMaps.txt Edit (18.2 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (3.9 KiB, text/plain; charset="utf-8")
- ProcStatus.txt Edit (766 bytes, text/plain; charset="utf-8")
- UdevLog.txt Edit (356.7 KiB, text/plain; charset="utf-8")
- XorgLog.txt Edit (40.8 KiB, text/plain; charset="utf-8")
- XorgLogOld.txt Edit (42.2 KiB, text/plain; charset="utf-8")
- i915_error_state.txt Edit (2.2 MiB, text/plain; charset="utf-8")
Launchpad Janitor (janitor) wrote : | #2 |
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | New → Confirmed |
tags: | removed: need-duplicate-check |
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #25 |
Created attachment 66289
dmesg output
From time to time interface freezes, and in dmesg appear these records: [drm:i915_
$ lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 PCI bridge: ASMedia Technology Inc. Device 1080 (rev 01)
03:01.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
04:00.0 Ethernet controller: Atheros Communications AR8151 v2.0 Gigabit Ethernet (rev c0)
05:00.0 USB Controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
06:00.0 SATA controller: ASMedia Technology Inc. Device 0612 (rev 01)
Bryce Harrington (bryce) wrote : | #3 |
Does switching from UXA to SNA help?
Changed in xserver-xorg-video-intel (Ubuntu): | |
importance: | Undecided → Medium |
Rocko (rockorequin) wrote : | #4 |
Ha! I thought SNA was turned on by default, but it isn't, is it. Is it possible to switch between SNA and UXB on when X is running, or to tell which one is being used?
I've turned SNA on via AccelMethod in xorg.conf now, so I'll see if the freezes go away.
Since I restarted X with SNA, the titlebar of windows that don't have the focus change their background to light grey. The window buttons and the title text stay the same, which looks weird. Is that something that can be configured?
Rocko (rockorequin) wrote : | #5 |
Is SNA turned on by default now? I had a couple of hours freeze-free with it the other day, but removed my xorg.conf shortly afterwards because the white titlebars and glitchy 3D graphics were annoying, and also because with SNA enabled the backlight didn't come on after the screensaver turned it off. But now the titlebars are white again.
Bryce Harrington (bryce) wrote : | #6 |
SNA is not the default for quantal. No, there is not a way to toggle between UXA and SNA at run time. /var/log/Xorg.0.log is where to look to see which acceleration tech is active.
If I understand your testing feedback, you do believe SNA helps eliminate the freeze behaviors, and thus we can consider UXA the likely source of the bug.
Rocko (rockorequin) wrote : | #7 |
Yes, I think the bug doesn't happen with SNA whereas it occurs pretty regularly with UXA. I've been using SNA for a couple of days now since it became the default on my system. Does X now look for other xorg.conf files? I created one called /etc/X11/
Rocko (rockorequin) wrote : | #8 |
Ah, I am using xorg-edgers. Perhaps they are trying out SNA as the default there.
Rocko (rockorequin) wrote : | #9 |
I've been using SNA for a couple of weeks now, and it doesn't seem to suffer from this particular bug.
The bug still occurs in the latest xf86-video-intel driver from git (as of 27/9/12), though. It generally occurs when focus changes, eg when a menu or popup window is opening.
Ursula Junque (ursinha) wrote : | #10 |
Hi Bryce, I've been getting this error every once in a while and when it happens, apport tries to report the bug like ten times. Let me know if I can provide more information about it.
Cheers,
Ursula Junque (ursinha) wrote : | #11 |
I've filed another bug with apport and all my files are attached there: bug 1059737, just in case they're not duplicates.
Paul Smedley (paul-smedley) wrote : | #12 |
Switching from UXA to SNA fixes this for me too, on an Asus Zenbook UX31E
Dimitri John Ledkov (xnox) wrote : | #13 |
I am hitting this bug. Can somebody please explain how to check if I am using UXA or SNA and how to switch between the two? If SNA helps, and I am using UXA I'd like to try SNA.
Rocko (rockorequin) wrote : | #14 |
@Dmitrijs: To find which method is being used, do:
grep AccelMethod /var/log/Xorg.0.log
I find also that the titlebars of non-focused windows are often light grey instead of black when using SNA.
And to change methods, put this in your xorg.conf to set the acceleration method and then restart X:
Section "Device"
Identifier "Card0"
Driver "intel"
Option "AccelMethod" "sna" # or uxa, as appropriate
EndSection
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #26 |
If you can easily reproduce this error, can you please build a kernel using http://
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #27 |
Can you help me to build rpm for fedora?
Rocko (rockorequin) wrote : | #15 |
I still experience this bug, even with the latest intel driver from git, xf86-video-
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #28 |
On second thoughts, I think this should be fixed by the slight robustification in more recent hangcheck.
Please try the latest kernel for your distribution (should be 3.6.7 atm) and reopen if it still occurs.
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #29 |
I am use Fedora 18 with 3.6.7-5.fc18.i686 kernel and in dmesg output still exists message:
[22826.654365] [drm:i915_
[22826.654369] [drm] capturing error event; look for more information in /debug/
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #30 |
That is not the same bug, so you need to attach a fresh set of debug info (please remember the i915_error_
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #31 |
Please, explain how get needed debug info. Thanks.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #32 |
http://
From which we need the i915_error_state, so
$ sudo mount -tdebugfs debug /sys/kernel/debug
$ sudo cat /sys/kernel/
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #33 |
Created attachment 70518
i915_error_state
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #34 |
Looks that corresponds to the bug
commit 1c8b46fc8c86518
Author: Chris Wilson <email address hidden>
Date: Wed Nov 14 09:15:14 2012 +0000
drm/i915: Use LRI to update the semaphore registers
The bspec was recently updated to remove the ability to update the
semaphore using the MI_SEMAPHORE_BOX command, the ability to wait upon
the semaphore value remained. Instead the advice is to update the
register using the MI_LOAD_
semaphores continue to function - the question is whether this fixes
some of the deadlocks where the semaphore registers contained stale
values?
hopefully addresses.
That patch is only available on drm-intel-next at the moment, which is available either at http://
tags: | added: raring |
Timo Aaltonen (tjaalton) wrote : | #16 |
I've uploaded -intel 2.20.14 to raring, so please test with both UXA and SNA to see if either or both work.
Rocko: I can't reproduce your bug with SNA (with this new version anyway), works fine on my T420s. 2.6.99.902 sounds old too :)
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Confirmed → Incomplete |
Rocko (rockorequin) wrote : | #17 |
Yes, I've been running v2.20.14 from git (using SNA, not UXA) for a few days on Quantal and so far I hasn't seen that other bug I mentioned - it hasn't fatally locked up after the screensaver kicks in. However, it has experienced *this* particular bug a few times, ie where the screen locks but I can fix it by switching to a tty terminal and back.
Re 2.6.99.902, I think I probably did a git tag command and looked at the last entry, which is definitely old. I would have been running a pre-v2.20.14 version at the time.
Karma Dorje (taaroa) wrote : | #18 |
@Timo Aaltonen
SNA — ok. looks like some sort of regression in the driver.
Bryce Harrington (bryce) wrote : | #19 |
Rocko, thanks for testing the git DDX. Next time you get one of these freezes can you please collect a fresh i915_error_state, dmesg, and Xorg.0.log?
Sounds like this bug should go upstream.
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #35 |
Problem repeated with patched kernel.
[118637.439016] [drm:i915_
[118637.439020] [drm] capturing error event; look for more information in /debug/
[mikhail@localhost ~]$ uname -a
Linux localhost.
[mikhail@localhost ~]$ sudo cat /sys/kernel/
[sudo] password for mikhail:
[mikhail@localhost ~]$
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #36 |
Created attachment 71192
i915_error_state (new)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #37 |
sudo cat /sys/kernel/
cat: /sys/kernel/
What it mean??
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #38 |
Created attachment 71199
i915_error_state (new)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #39 |
Created attachment 71200
dmesg output (new)
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #40 |
Lalalalala.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #41 |
*** Bug 58057 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #42 |
*** Bug 58212 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #43 |
We can confirm the synopsis by disabling semaphores (i915.semaphore=0), but can we also test whether this is an rc6 side-effect (i915.i915_
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #44 |
Also maybe time for ' git revert 4e0e90dcb8a7df1
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #45 |
Created attachment 71549
i915_error_state
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #48 |
Created attachment 71630
dmesg
bugbot (bugbot) wrote : | #20 |
We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.
Some tips:
* Report X.org bugs via the command: `ubuntu-bug xorg`
* Test against the latest development Ubuntu. http://
Bugs marked as affecting the development version tend to get priority attention.
* The `xdiagnose` utility has functionality for enabling debugging and
analyzing a few common X problems.
* Tag your bugs with the Ubuntu versions you have reproduced the issue in.
* See https:/
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Incomplete → Expired |
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Expired → Confirmed |
Changed in xserver-xorg-video-intel (Ubuntu): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
status: | Confirmed → Incomplete |
Rocko (rockorequin) wrote : | #23 |
I've seen it happen with kernel 3.8-rc2 and SNA using the latest intel driver from git.
The hang isn't always the same:
* Sometimes it locks the computer up completely, requiring a hard reboot.
* Sometimes it locks X, but CTRL-ALT-F1 and back unlocks it.
* Sometimes it resolves itself without me even noticing that it has happened, other than that there may be some corruption in the tabs' title text in chrome and window movement has become somewhat jerky instead of the normal smooth movement you get after restarting X.
Next time it happens I'll see if I can recover any information.
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #52 |
(In reply to comment #24)
> Mikhail, for the time being you can set i915.semaphores=0 (or echo 0 >
> /sys/modules/
What are the consequences?
> The only interesting patch I can suggest atm is
>
> commit 31643d54a739382
> Author: Ben Widawsky <email address hidden>
> Date: Wed Sep 26 10:34:01 2012 -0700
>
> drm/i915: Workaround to bump rc6 voltage to 450
>
> BIOS should be setting the minimum voltage for rc6 to be 450mV. Old or
> buggy BIOSen may not be doing this, so we correct it for them. Ideally
> customers should update the BIOS as only it would know the optimal
> values for the platform, so we leave that fact as a DRM_ERROR for the
> user to see.
>
> in 3.8-rc1 or look for a BIOS update.
I have H61M/U3S3 motherboard and you latest BIOS ver 2.20 from 8/15/2012
ftp://174.
How to check problem persists or not?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #53 |
(In reply to comment #27)
> (In reply to comment #24)
> > Mikhail, for the time being you can set i915.semaphores=0 (or echo 0 >
> > /sys/modules/
>
> What are the consequences?
Rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption.
Adam Conrad (adconrad) wrote : | #24 |
Timo: I've never had it completely hang the machine, but I've also not been patient enough to sit around and wait to see if X will eventually recover on its own, I always do a VT switch out and back (and get welcomed by an apport dialog)
Has happened several times today. Will be upgrading to 3.8.0-rc soon to see if that helps, but the comment above me doesn't give much hope.
Changed in xserver-xorg-video-intel: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Timo Aaltonen (tjaalton) wrote : Re: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 | #54 |
ok, so the hang I'm seeing is this same one, not that frequent though
Roman Yepishev (rye) wrote : | #55 |
I've started getting this failure after migrating to Raring and I get the recoverable lockups 3 times a day or even more with the same GPU lockup message in dmesg. Apport has proposed [sandybridge-
I am using 3.8.0-0-generic kernel.
There is no AccelMethod string in Xorg log (so it should be uxa), will check whether this happens with sna.
In freedesktop.org Bugzilla #54226, bwidawsk (bwidawsk) wrote : | #56 |
(In reply to comment #27)
> > The only interesting patch I can suggest atm is
> >
> > commit 31643d54a739382
> > Author: Ben Widawsky <email address hidden>
> > Date: Wed Sep 26 10:34:01 2012 -0700
> >
> > drm/i915: Workaround to bump rc6 voltage to 450
> >
> > BIOS should be setting the minimum voltage for rc6 to be 450mV. Old or
> > buggy BIOSen may not be doing this, so we correct it for them. Ideally
> > customers should update the BIOS as only it would know the optimal
> > values for the platform, so we leave that fact as a DRM_ERROR for the
> > user to see.
> >
> > in 3.8-rc1 or look for a BIOS update.
>
> I have H61M/U3S3 motherboard and you latest BIOS ver 2.20 from 8/15/2012
> ftp://174.
> How to check problem persists or not?
The easiest way is to apply the patch and look for DRM_DEBUG_DRIVER messages. This is unlikely to fix the problem, but also can't hurt.
We've only assumed new BIOS will fix the problem, but who knows. Especially if it's a 3rd party BIOS.
Changed in xserver-xorg-video-intel (Ubuntu): | |
importance: | Medium → High |
status: | Incomplete → Triaged |
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : Re: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 | #57 |
I'm seeing this on an X220 running up to date raring. Happens a few times a day. .
alan@deep-
[ 12.175] (II) intel(0): SNA compiled: xserver-
[ 13.744] (II) intel(0): SNA initialized with SandyBridge backend
alan@deep-
alan@deep-
alan@deep-
Pretty sure I have the very latest BIOS from Lenovo as I recently installed Windows on the machine to do exactly that.
Timo Aaltonen (tjaalton) wrote : | #58 |
try 'echo 0 > /sys/module/
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Triaged → Confirmed |
Timo Aaltonen (tjaalton) wrote : | #59 |
..and restart X (logging out should do it when lightdm is used)
Timo Jyrinki (timo-jyrinki) wrote : | #60 |
My first of this type happened today, even though I've already been using SNA before since August or so. If this now starts to be recurring (since I also started to have bug #1102390 only yesterday), I can try disabling the semaphores.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #62 |
*** Bug 59786 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #63 |
Created attachment 73560
write mbox regs twice on snb
Another piece of magic which might help. Please test this patch and the one from Chris ("Read back semaphore mboxes after update") separately and report back whether anything changes.
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #64 |
Created attachment 73577
write mbox regs twice on snb, v2
Now actually the right patch attached, the old one didn't compile ...
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : | #61 |
The workaround in comment #58 does eliminate the GPU lockups. Which I notice when I boot in the morning and forget to do that workaround and get a lockup part way through the day.
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #65 |
Which patch I need applied for fix this issue?
I see that patches from comment 26 and 32 have similar logic...
@@ -596,6 +606,16 @@ gen6_add_
intel_
intel_
+ if (IS_GEN6(
+ ret = intel_ring_
+ if (ret)
+ return ret;
+
+ read_mboxes(ring, mbox1_reg, 1024);
+ read_mboxes(ring, mbox2_reg, 1028);
+ intel_ring_
+ }
+
return 0;
}
@@ -598,6 +598,19 @@ gen6_add_
intel_
intel_
+ if (IS_GEN6(
+ ret = intel_ring_
+ if (ret)
+ return ret;
+
+ mbox1_reg = ring->signal_
+ mbox2_reg = ring->signal_
+
+ update_mboxes(ring, mbox1_reg);
+ update_mboxes(ring, mbox2_reg);
+ intel_ring_
+ }
+
return 0;
}
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #66 |
> --- Comment #33 from <email address hidden> ---
> Which patch I need applied for fix this issue?
We can't reproduce the bug, so those are just patches to test
different ideas. Please test them both each individually (i.e. remove
the first before testing the 2nd patch) and the report whether
anything changes (i.e. harder or easier for you to hit the issue).
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #67 |
Can't compile kernel with patch above:
drivers/
drivers/
drivers/
drivers/
drivers/
make[4]: *** [drivers/
make[3]: *** [drivers/
make[2]: *** [drivers/gpu/drm] Error 2
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | Confirmed → Triaged |
In freedesktop.org Bugzilla #54226, Norman Yarvin (yarvin-yarchive) wrote : | #75 |
I'm seeing this bug, or something like it, on an older chip (G965, desktop version):
Feb 19 22:05:56 muttonhead kernel: [drm:i915_
Feb 19 22:05:56 muttonhead kernel: [drm] capturing error event; look for more information in /debug/
Feb 19 22:05:56 muttonhead kernel: [drm:kick_ring] *ERROR* Kicking stuck wait on render ring
Feb 19 22:05:57 muttonhead kernel: [drm:i915_reset] *ERROR* Failed to reset chip.
after which the mouse pointer sticks in one spot (with most other things working), and then when I shut down X, the console fails to appear, requiring a reboot. Not knowing that the given file path was under /sys/kernel, I failed to capture the error state, but will do so next time this happens (which is maybe every other day). This is with a 3.7 kernel (Gentoo); before 3.7, the driver was stable. I don't know what the 'generation' numbers in the driver mean, but I'm guessing that generation 6 is later, so many of the suggested fixes would not make any difference on this machine.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #76 |
(In reply to comment #42)
> I'm seeing this bug, or something like it, on an older chip (G965, desktop
> version):
Good news, it is not this bug. Please make sure you have the latest stable driver (a gentoo user not using 3.8 already! ;-) and latest xf86-video-intel, then file a fresh bug report, attaching your dmesg, Xorg.0.log and i915_error_state.
In freedesktop.org Bugzilla #54226, gneman (luis6674) wrote : | #77 |
I subscribed to this bug because I was seeing this hang too. It happened randomly several times, without a specific cause or way to reproduce it.
This was around December, and it happened maybe 4-5 times along a month. The GPU would hang with that error in dmesg, and everything continued to work, though very slowly.
However, I must say that since then it didn't happen again for almost 2 months maybe. I use Arch Linux, which means I always update to the latest stable packages of everything, so it seems that for me it got solved at some point (or at least much harder to reproduce).
This is an Ironlake / HD 2000 based Dell laptop. I did update the BIOS when I found this bug report, but it didn't solve the problem, the hang happened after updating it.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #78 |
*** Bug 61310 has been marked as a duplicate of this bug. ***
Laura Czajkowski (czajkowski) wrote : Re: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 | #74 |
This bug has started to affect me on 13.04
summary: |
- [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 + [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround + i915.semaphores=0 |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Brad Figg (brad-figg) wrote : Status changed to Confirmed | #79 |
This change was made by a bot.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #86 |
Created attachment 75818
i915_error_state (kernel 3.8.1 Fedora)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #87 |
Today Fedora 18 updated kernel to 3.8.1 and message "[drm:i915_
Pete Graner (pgraner) wrote : | #80 |
GPU is locking up numerous times a day, just started on Raring. Apport is telling me my bug has already been reported and points me at https:/
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : | #81 |
@pgraner I have the same GPU lockup frequently, daily. I sometimes forget to set the workaround i915.semaphores to 0, but when I do the lockups go away. I have now set it in the /etc/default/grub as GRUB_CMDLINE_
Robin Munn (rmunn) wrote : | #82 |
I've been experiencing a recurring lockup that may or may not be this bug; what I can add to the discussion is that if it is this bug, it appears to be Linux-only. My company bought several of its developers identical laptops (Dell Latitude E6520 models). The other developers who are using these laptops are using Windows, and I'm the only one using Linux. I've been experiencing these hangups 3-4 times per week, on average, over the past year. But when I asked the other developers in my company with Latitude E6520s if they'd experienced random-seeming hangups, they all said no. Which means that either I got the only laptop with a defective chip, or else the Windows driver doesn't experience this problem.
I hope this helps in some way; sorry I can't be of more technical help, but GPUs are outside my area of expertise.
In freedesktop.org Bugzilla #54226, bwidawsk (bwidawsk) wrote : | #88 |
This looks weird to me:
0x00005a58: 0x11000001: MI_LOAD_
0x00005a5c: 0x00012044: dword 1
0x00005a60: 0x0043b625: dword 2
0x00005a64: 0x11000001: MI_LOAD_
0x00005a68: 0x00022040: dword 1
0x00005a6c: 0x0043b625: dword 2
0x00005a70: 0x10800001: MI_STORE_DATA_INDEX
0x00005a74: 0x00000080: index
0x00005a78: 0x0043b625: dword
0x00005a7c: 0x01000000: MI_USER_INTERRUPT
0x00005a80: 0x0b160001: MI_SEMAPHORE_MBOX compare semaphore, use compare reg 2
0x00005a84: 0x0043b625: value
0x00005a88: 0x00000000: address
0x00005a8c: 0x00000000: MI_NOOP
Chris?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #89 |
Weird? Did you just forget about that the hw does a strictly greater-than comparison?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #90 |
(In reply to comment #47)
> Today Fedora 18 updated kernel to 3.8.1 and message
> "[drm:i915_
> still here. Please look at my last log. Any updates?
We're still waiting upon you apply patches and report.
Stan Schymanski (schymans) wrote : | #83 |
- drm:i915_hangcheck_hung and following messages in kern.log before permanent lock-up Edit (6.3 KiB, text/plain)
I experienced a permanent GPU lock-up today, the screen was unresponsive for half an hour before I decided to reboot by pressing Alt+SysRq-REISUB. The below is the the relevant section of kern.log before shutting down.
Stan Schymanski (schymans) wrote : | #84 |
Just to add some background information to my previous post:
I have been having random hangups for more than a year now, but only since the beginning of this week, I have been getting the GPU hang-up error messages. Today, it coincided with one of the complete lock-ups, that could only be resolved by Alt+SysRq-REISUB. I will now try the approach proposed in Comment #81, hoping for the best. I hope that I am not seeing two different issues here. The GPU hang-up error message has been reoccurring without obvious hang-ups in the past few days, while my complete hang-ups have been happening randomly, sometimes with the possibility to reboot as outlined above, sometimes without (only the power button would do) and sometimes the computer turned itself off without any interaction from my side...
If anyone sees anything new in the kern.log section I pasted, please let me know.
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #91 |
*** Bug 61925 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #92 |
Created attachment 76196
i915_error_state (kernel 3.8.1 Fedora) with path (write mbox regs twice on snb, v2)
I am applied patch "write mbox regs twice on snb, v2" but still have problem [drm:i915_
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #93 |
Created attachment 76208
i915_error_state (kernel 3.8.1 Fedora) with path (Read back semaphore mboxes after update)
I am also applied patch "Read back semaphore mboxes after update" but still have problem [drm:i915_
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #94 |
(In reply to comment #52)
> Created attachment 76196 [details]
> i915_error_state (kernel 3.8.1 Fedora) with path (write mbox regs twice on
> snb, v2)
>
> I am applied patch "write mbox regs twice on snb, v2" but still have problem
> [drm:i915_
0x00052cc8: 0x18800100: MI_BATCH_
0x00052ccc: 0x0d59b000: dword 1
0x00052cd0: 0x13000001: MI_FLUSH_DW post_sync_op='no write'
0x00052cd4: 0x000000c4: address
0x00052cd8: 0x00000000: dword
0x00052cdc: 0x00000000: MI_NOOP
0x00052ce0: 0x11000001: MI_LOAD_
0x00052ce4: 0x00002044: dword 1
0x00052ce8: 0x0007a582: dword 2
0x00052cec: 0x11000001: MI_LOAD_
0x00052cf0: 0x00012040: dword 1
0x00052cf4: 0x0007a582: dword 2
0x00052cf8: 0x10800001: MI_STORE_DATA_INDEX
0x00052cfc: 0x00000080: index
0x00052d00: 0x0007a582: dword
0x00052d04: 0x01000000: MI_USER_INTERRUPT
That's only a single LRI per semaphore, the patch wasn't tested.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #95 |
I would say '3.8.1-
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #96 |
Created attachment 76215
kernel.spec
(In reply to comment #55)
> I would say '3.8.1-
> patched version.
It's impossible. Distro kernel is 3.8.1-201.
You can sure if look at my build spec file.
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #97 |
Created attachment 76239
i915_error_state (kernel 3.8.1 Fedora) with path (Read back semaphore mboxes after update)
I am sorry. Seems I forgot add "ApplyPatch" to spec. I am rebuild kernel with "0001-drm-
Does it make sense to check the "0001-write-
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #98 |
Created attachment 76243
i915_error_state (kernel 3.8.1 Fedora) with path (Read back semaphore mboxes after update)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #99 |
Created attachment 76261
i915_error_state (kernel 3.8.2 Fedora) with path (write mbox regs twice on snb, v2)
"write mbox regs twice on snb, v2" patch also not solve problem.
[ 1399.270341] [drm:i915_
[ 1399.270345] [drm] capturing error event; look for more information in /debug/
[ 1399.277331] [drm:__
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #100 |
Created attachment 76293
i915_error_state (kernel 3.8.2 Fedora) with path (write mbox regs twice on snb, v2)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #108 |
Created attachment 76448
i915_error_state (kernel 3.8.2 Fedora) with path (write mbox regs twice on snb, v2)
Any updates?
Stan Schymanski (schymans) wrote : | #101 |
GPU -lockup messages started re-appearing, despite an Upgrade to Kernel 3.8.2 in Ubuntu 12.10.
Chris Wilson (ickle) wrote : | #102 |
#81 is only applicable to this bug, and is the correct workaround. Not all GPU hangs are this bug, most tend to be mesa...
Stan Schymanski (schymans) wrote : | #103 |
Sorry, I haven't been able to attach any of the crash reports, because I get the message that the crash relates to Bug #1059737 and I don't get an opportunity to upload the report. Bug #1059737 is supposed to be a duplicate of this bug, which is why I started posting here. How can I verify whether it is this bug or a mesa bug?
Chris Wilson (ickle) wrote : | #104 |
The most brutal way would be to remove /usr/lib/
Stan Schymanski (schymans) wrote : | #105 |
Before I do this, could you confirm whether my new report of Bug #1154591 is related to this here or not? Should I still try removing i965_dri.so, or has this become irrelevant?
Chris Wilson (ickle) wrote : | #106 |
Easy answer: probably. Impossible to tell without the error-state.
Bilal Shahid (s9iper1) wrote : | #107 |
here is another bug and i frequently having this hang recently it hanged again
and i didnt report the new ones bug it open the link into the previous bug 1153202
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #109 |
*** Bug 62443 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #111 |
As a workaround, this
commit a24a11e6b4e96bc
Author: Chris Wilson <email address hidden>
Date: Thu Mar 14 17:52:05 2013 +0200
drm/i915: Resurrect ring kicking for semaphores, selectively
should improve the recovery from the hangs.
Launchpad Janitor (janitor) wrote : | #110 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in sandybridge-meta (Ubuntu): | |
status: | New → Confirmed |
In freedesktop.org Bugzilla #54226, cbrnr (cbrnr) wrote : | #112 |
OK, I've been experiencing this bug from time to time on my Arch Linux box. No apparent reason, last time it happened I was watching a Youtube video, and it also seems to happen more often when I'm running VirtualBox. However, this might just be a coincidence.
In freedesktop.org Bugzilla #54226, Longerdev (longerdev) wrote : | #114 |
I have this bug too.
Gentoo 64bit
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd Device c0a0
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f5c00000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at e000 [size=64]
Expansion ROM at <unassigned> [disabled]
Kernel driver in use: i915
Kernel 3.8.0 gentoo-sources
I try patch a24a11e6b4e96bc
Mar 31 15:14:37 localhost kernel: [64379.291736] [drm:i915_
Mar 31 15:14:37 localhost kernel: [64379.291742] [drm] capturing error event; look for more information in /debug/
Spencer Mabrito (xoptics) wrote : | #113 |
Just some further confirmation of this issue.
On a Sandy Bridge i5 Dell Latitude e6420 laptop with Intel HD 4000 integrated graphics. On 3.5.0-26-generic I experienced GPU hangs once or twice an hour (fixed themselves after a few seconds) and full lockups 2 to 5 times per day, depending on what I was doing (have to hard reboot the machine to recover). Having firefox open seemed to be a risk factor, and if FF had loaded flashplayer, I expected a full lockup at any moment.
As described in the following bug, which is a similar issue... https:/
i915.semaphores=0
This decreased the frequency and severity of lockups/crashes, but they were still there. Upon further investigation, I found this bug to be the actual issue (my syslog showing the same 3 lines as the others in this thread), and have reverted to 3.5.0-25-generic and have been running without any issues for a day or two now. I still have i915-semaphores=0 in my grub boot options but don't think I still need that...
In freedesktop.org Bugzilla #54226, Mika-kuoppala (mika-kuoppala) wrote : | #119 |
Created attachment 77475
[PATCH] drm/i915: Resurrect ring kicking for semaphores, selectively
In freedesktop.org Bugzilla #54226, Mika-kuoppala (mika-kuoppala) wrote : | #120 |
(In reply to comment #61)
> Created attachment 76448 [details]
> i915_error_state (kernel 3.8.2 Fedora) with path (write mbox regs twice on
> snb, v2)
>
> Any updates?
Mikhail,
Could you please try patch:
[PATCH] drm/i915: Resurrect ring kicking for semaphores, selectively
description: | updated |
description: | updated |
description: | updated |
description: | updated |
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #121 |
Patch is also included in latest drm-intel-nightly, linux-next. So you can test it by grabbing a distro-build of one of those.
description: | updated |
Changed in linux (Ubuntu): | |
status: | Invalid → New |
Bryce Harrington (bryce) wrote : | #115 |
@kernel team - comment #111 has a test patch worth having a kernel built for that folks can test.
Brad Figg (brad-figg) wrote : Status changed to Confirmed | #116 |
This change was made by a bot.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Seth Forshee (sforshee) wrote : | #117 |
I've built a quantal kernel with the patch mentioned on the freedesktop.org bugzilla. Please test to see if it resolves the issue.
http://
Compiler issues are preventing me from building for raring atm, but I'll post a raring build as soon as I am able to do so.
In freedesktop.org Bugzilla #54226, Brian Ealdwine (eode) wrote : | #118 |
Occurred while playing vessel. Never ran into the problem on 12.10.
I'm available to provide info.
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → Incomplete |
Seth Forshee (sforshee) wrote : | #122 |
A test build for raring is now available.
http://
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #123 |
(In reply to comment #67)
> (In reply to comment #61)
> > Created attachment 76448 [details]
> > i915_error_state (kernel 3.8.2 Fedora) with path (write mbox regs twice on
> > snb, v2)
> >
> > Any updates?
>
> Mikhail,
>
> Could you please try patch:
> [PATCH] drm/i915: Resurrect ring kicking for semaphores, selectively
Hm, seems better but problem still here
[59120.008798] [drm:i915_
[59120.008802] [drm] capturing error event; look for more information in /debug/
[59120.012173] [drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #124 |
Created attachment 77692
i915_error_state (kernel 3.8.5 Fedora) with path (drm/i915: Resurrect ring kicking for semaphores, selectively)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #125 |
Created attachment 77693
dmesg (kernel 3.8.5 Fedora) with path (drm/i915: Resurrect ring kicking for semaphores, selectively)
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #126 |
\o/ It kicked the right ring.
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #127 |
(In reply to comment #72)
> \o/ It kicked the right ring.
So is this normal?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #128 |
It's the expected 'improved' recovery behaviour for this bug.
Changed in xserver-xorg-video-intel: | |
status: | Incomplete → Confirmed |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #129 |
*** Bug 63542 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Bryce Harrington (bryce) wrote : | #130 |
Chris, what is the upstream status for the ring kicker patch? Is that likely to get incorporated upstream, or do you feel it needs further polish before it's ready? Would this patch incur some risk of regressions in other areas were it be backported for inclusion in Ubuntu?
tags: | added: kernel-handoff-graphics |
Chris Wilson (ickle) wrote : | #131 |
The ring kicker is upstream, but it is not a fix. It is just a ligherweight reset mechanism that should prevent a cascade of errors and corruption - but the user still suffers the 3s stall before the hang is detected.
However, the patch seems to be solid and has survived its trial by fire.
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #132 |
(In reply to comment #76)
> Chris, what is the upstream status for the ring kicker patch? Is that
> likely to get incorporated upstream, or do you feel it needs further polish
> before it's ready? Would this patch incur some risk of regressions in other
> areas were it be backported for inclusion in Ubuntu?
Merged for 3.10 as
commit a24a11e6b4e96bc
Author: Chris Wilson <email address hidden>
Date: Thu Mar 14 17:52:05 2013 +0200
drm/i915: Resurrect ring kicking for semaphores, selectively
Nothing else planned for now, but I think we can just keep this bug here open in case we stumble across a new idea. And it seems to be good honey to attrack all the me,too reports ;-)
In freedesktop.org Bugzilla #54226, Tomwij-1 (tomwij-1) wrote : | #133 |
(In reply to comment #65)
> Kernel 3.8.0 gentoo-sources
Did you report this at the Gentoo Bugzilla?
When you do, please attach /debug/
In freedesktop.org Bugzilla #54226, Longerdev (longerdev) wrote : | #134 |
>Did you report this at the Gentoo Bugzilla?
>When you do, please attach /debug/
Now no report in gentoo bugzilla (so as in kernel they no have patches intel drivers). But now with it patch, I can't repeat bug 2 weeks on kernel 3.9-rc6. But I no test with blender (when I try use blender, GPU hung reapeted for 1-5 minutes).
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #135 |
*** Bug 64094 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #136 |
Created attachment 78692
i915_error_state (kernel 3.9 Fedora)
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #137 |
Created attachment 78693
i915_error_state (kernel 3.9 Fedora)
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #138 |
*** Bug 64094 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Freedesktop-l (freedesktop-l) wrote : | #139 |
Created attachment 79704
i915_error_state - kernel 3.10-rc2, dual monitor, Dell E6430
I can reproduce this bug every time I try to quickly drag a Chrome window with a YouTube movie to a secondary monitor connected to my laptop Dell E6430. It is very annoying. Tested on latest kernel 3.10-rc2.
I can give you any additional information you want, test patches, etc. Just please try to fix this :)
In freedesktop.org Bugzilla #54226, Freedesktop-l (freedesktop-l) wrote : | #140 |
(In reply to comment #84)
> Created attachment 79704 [details]
> i915_error_state - kernel 3.10-rc2, dual monitor, Dell E6430
>
> I can reproduce this bug every time I try to quickly drag a Chrome window
> with a YouTube movie to a secondary monitor connected to my laptop Dell
> E6430.
One more information - you need to enable "Override software rendering list" in chrome://flags
Dac Chartrand (conner-bw) wrote : | #141 |
Came here from bug #1129679 which more accurately describes my problem. Apparently that bug is a this is a dupe of this bug which IMHO is not really the same, but whatever...
I'm running 13.03 on Lenovo X220
Has anyone looked at?
https:/
Did this patch get lost along the way?
Regards,
In freedesktop.org Bugzilla #54226, Cwawak (cwawak) wrote : | #142 |
Created attachment 79979
i915_error_state - 3.9.2-201.
Linux bobloblaw 3.9.2-201.
[45482.757631] [drm:i915_
[45482.757645] [drm] capturing error event; look for more information in/sys/
[45482.766942] [drm:kick_ring] *ERROR* Kicking stuck semaphore on render ring
[45482.770617] [drm:__
I added patch (drm/i915: Resurrect ring kicking for semaphores, selectively) to Fedora 18's 3.9.2-200 x86_64 kernel.
In freedesktop.org Bugzilla #54226, Cwawak (cwawak) wrote : | #143 |
Is there any input or assistance I can give to help move this along?
Thanks!
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #144 |
Created attachment 82747
New read-after-write patch
New patch for testing, thanks!
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #145 |
Created attachment 82748
New read-after-write patch
In freedesktop.org Bugzilla #54226, Mikhail Gavrilov (mikegav) wrote : | #146 |
For which version of the kernel this patch?
In freedesktop.org Bugzilla #54226, Longerdev (longerdev) wrote : | #147 |
I tried it patch on linux-3.11_rc1, but when X starting I see:
791966 Jul 21 16:17:07 localhost kernel: [ 19.320879] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
791967 Jul 21 16:17:07 localhost kernel: [ 19.320948] IP: [<ffffffff8136b
791968 Jul 21 16:17:07 localhost kernel: [ 19.320995] PGD b0d80067 PUD b0c18067 PMD 0
791969 Jul 21 16:17:07 localhost kernel: [ 19.321031] Oops: 0000 [#1] PREEMPT SMP
791970 Jul 21 16:17:07 localhost kernel: [ 19.321064] Modules linked in: snd_hda_codec_hdmi snd_hda_
791971 Jul 21 16:17:07 localhost kernel: [ 19.321209] CPU: 0 PID: 2696 Comm: X Not tainted 3.11.0-rc1 #1
791972 Jul 21 16:17:07 localhost kernel: [ 19.321249] Hardware name: SAMSUNG ELECTRONICS CO., LTD. SF311/SF411/
791973 Jul 21 16:17:07 localhost kernel: [ 19.321322] task: ffff8800b1c07590 ti: ffff8800b0c24000 task.ti: ffff8800b0c24000
791974 Jul 21 16:17:07 localhost kernel: [ 19.321370] RIP: 0010:[<
791975 Jul 21 16:17:07 localhost kernel: [ 19.321426] RSP: 0018:ffff8800b0
791976 Jul 21 16:17:07 localhost kernel: [ 19.321461] RAX: 0000000000000000 RBX: ffff8800b1c3d4d8 RCX: 0000000000027330
791977 Jul 21 16:17:07 localhost kernel: [ 19.321506] RDX: 0000000000000080 RSI: ffffc900045c003c RDI: ffffc900045c0038
791978 Jul 21 16:17:07 localhost kernel: [ 19.321550] RBP: ffff8800b0c25c08 R08: ffff8800b0d97f00 R09: 00000000000145c0
791979 Jul 21 16:17:07 localhost kernel: [ 19.321594] R10: 0000000000001000 R11: ffff8800b1c3c000 R12: 0000000000000000
791980 Jul 21 16:17:07 localhost kernel: [ 19.321638] R13: 0000000000002044 R14: 0000000000000000 R15: ffff8800b1c3c000
791981 Jul 21 16:17:07 localhost kernel: [ 19.321682] FS: 00007ff167ae888
791982 Jul 21 16:17:07 localhost kernel: [ 19.321732] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
791983 Jul 21 16:17:07 localhost kernel: [ 19.321767] CR2: 0000000000000010 CR3: 00000000b1cc9000 CR4: 00000000000407f0
791984 Jul 21 16:17:07 localhost kernel: [ 19.321810] Stack:
791985 Jul 21 16:17:07 localhost kernel: [ 19.321824] ffff8800b1c3d4d8 0000000000000000 ffff8800aff24000 0000000000000000
791986 Jul 21 16:17:07 localhost kernel: [ 19.321876] ffff8800b1c3c000 ffff8800b0d97f00 ffff8800b1f66a00 ffff8800b1c3d4d8
791987 Jul 21 16:17:07 localhost kernel: [ 19.321927] ffff8800b0c25c68 ffffffff81334b11 ffff880000000028 0000000000000000
791988 Jul 21 16:17:07 localhost kernel: [ 19.321979] Call Trace:
791989 Jul 21 16:17:07 localhost kernel: [ 19.322000] [<ffffffff81334
791990 Jul 21 16:17:07 localhost kernel: [ 19.322045] [<ffffffff8133b
791991 Jul 21 16:17:07 localhost kernel: [ 19.322089] [<ffffffff8133b
791992 Jul 21 1...
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #148 |
Created attachment 82768
New read-after-write patch
Oops, my mistake, please try again.
In freedesktop.org Bugzilla #54226, Longerdev (longerdev) wrote : | #149 |
Created attachment 82773
i915_error_state with new patch
(In reply to comment #92)
> Created attachment 82768 [details] [review]
> New read-after-write patch
>
> Oops, my mistake, please try again.
Now loading, but after five minutes test:
793485 Jul 21 17:32:56 localhost kernel: [ 321.432882] hda-intel 0000:00:1b.0: Unstable LPIB (32740 >= 4096); disabling LPIB delay counting
793486 Jul 21 17:34:49 localhost kernel: [ 434.291085] [drm:i915_
793487 Jul 21 17:34:49 localhost kernel: [ 434.291088] [drm] capturing error event; look for more information in /sys/kernel/
793488 Jul 21 17:34:49 localhost kernel: [ 434.307124] [drm:i915_
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #150 |
(In reply to comment #93)
> Created attachment 82773 [details]
> i915_error_state with new patch
>
> (In reply to comment #92)
> > Created attachment 82768 [details] [review] [review]
> > New read-after-write patch
> >
> > Oops, my mistake, please try again.
>
> Now loading, but after five minutes test:
> 793485 Jul 21 17:32:56 localhost kernel: [ 321.432882] hda-intel
> 0000:00:1b.0: Unstable LPIB (32740 >= 4096); disabling LPIB delay counting
> 793486 Jul 21 17:34:49 localhost kernel: [ 434.291085]
> [drm:i915_
> 793487 Jul 21 17:34:49 localhost kernel: [ 434.291088] [drm] capturing
> error event; look for more information in
> /sys/kernel/
> 793488 Jul 21 17:34:49 localhost kernel: [ 434.307124]
> [drm:i915_
> ctx 1) at 0xbfe21dc
That is a blorp (mesa/i965) bug and not the semaphore deadlock.
Tomasz Melcer (liori) wrote : | #151 |
I can reproduce this problem fairly regularly on a certain game inside wine (and nowhere else) on my up-to-date Debian Sid box. If there's any solution/patch to test and there's any benefit in testing it on a non-Ubuntu system, I volunteer to help.
Chris Wilson (ickle) wrote : | #152 |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #153 |
Will someone please try https:/
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → Incomplete |
In freedesktop.org Bugzilla #54226, Andy Lutomirski (luto-mit) wrote : | #154 |
The patch seems to have helped -- my box survived a couple days with the patch applied.
Changed in xserver-xorg-video-intel: | |
status: | Incomplete → Confirmed |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #155 |
The bad news is that I've just had the semaphore hang with all the read-after-write patch applied. :|
In freedesktop.org Bugzilla #54226, Januszmk6 (januszmk6) wrote : | #156 |
(In reply to comment #94)
> (In reply to comment #93)
> > Created attachment 82773 [details]
> > i915_error_state with new patch
> >
> > (In reply to comment #92)
> > > Created attachment 82768 [details] [review] [review] [review]
> > > New read-after-write patch
> > >
> > > Oops, my mistake, please try again.
> >
> > Now loading, but after five minutes test:
> > 793485 Jul 21 17:32:56 localhost kernel: [ 321.432882] hda-intel
> > 0000:00:1b.0: Unstable LPIB (32740 >= 4096); disabling LPIB delay counting
> > 793486 Jul 21 17:34:49 localhost kernel: [ 434.291085]
> > [drm:i915_
> > 793487 Jul 21 17:34:49 localhost kernel: [ 434.291088] [drm] capturing
> > error event; look for more information in
> > /sys/kernel/
> > 793488 Jul 21 17:34:49 localhost kernel: [ 434.307124]
> > [drm:i915_
> > ctx 1) at 0xbfe21dc
>
> That is a blorp (mesa/i965) bug and not the semaphore deadlock.
Could you please provide some link to this blorp bug report?
I had problem with semaphore deadlock, seems that with kernel 3.11 problem does not occur (without patch), but now I have:
[22221.843000] [drm:i915_
[22221.843483] [drm:i915_
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #157 |
*** Bug 68913 has been marked as a duplicate of this bug. ***
description: | updated |
In freedesktop.org Bugzilla #54226, Dan Doel (dan-doel) wrote : | #158 |
I have, I think, a reliable way to trigger this behavior, if that helps. It requires a non-trivial setup, though.
I have gnome-shell running on dual monitors. The first is 1920x1200, the second is 1920x1080 (not sure if the resolution difference matters). If I run a full-screen game on The 1920x1200 monitor, I get freezes, and notes in the dmesg about hangcheck timers and kickrings ("stuck wait on blitter ring").
I believe OpenGL acceleration of the desktop is important, because the freezes are not triggered in fluxbox, for instance. I'm not sure if the game itself needs to be using OpenGL, or if the full-screen window is the triggering factor, or something else entirely. It is important that the game keep the monitors distinct, and only go full screen on one. I just tried it on Battle for Wesnoth, and full screen there sets the monitors to mirror, which doesn't trigger the problem.
This is on an i7 4770, if that matters.
I realize this is may be difficult to put together for a test setup, but I thought I'd mention it.
In freedesktop.org Bugzilla #54226, Januszmk6 (januszmk6) wrote : | #159 |
(In reply to comment #100)
> I have, I think, a reliable way to trigger this behavior, if that helps. It
> requires a non-trivial setup, though.
>
> I have gnome-shell running on dual monitors. The first is 1920x1200, the
> second is 1920x1080 (not sure if the resolution difference matters). If I
> run a full-screen game on The 1920x1200 monitor, I get freezes, and notes in
> the dmesg about hangcheck timers and kickrings ("stuck wait on blitter
> ring").
>
> I believe OpenGL acceleration of the desktop is important, because the
> freezes are not triggered in fluxbox, for instance. I'm not sure if the game
> itself needs to be using OpenGL, or if the full-screen window is the
> triggering factor, or something else entirely. It is important that the game
> keep the monitors distinct, and only go full screen on one. I just tried it
> on Battle for Wesnoth, and full screen there sets the monitors to mirror,
> which doesn't trigger the problem.
>
> This is on an i7 4770, if that matters.
>
> I realize this is may be difficult to put together for a test setup, but I
> thought I'd mention it.
I also have dual monitors and also gnome-shell, but I have on both 1920x1080px. I notice that when I am watching some videos on full screen on one monitor, this is happening more often (on non full-screen work, it's still happening)
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #160 |
(In reply to comment #100)
> This is on an i7 4770, if that matters.
No, that's something completely new. Please open a new bug report and attach your dmesg, Xorg.0.log and /sys/drm/
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : | #161 |
I filed the duplicate of this bug 1222261 as I get this frequently on both my i7 laptop and i7 desktop.
I think I found a way to reproduce it easily on demand. Open chromium, and visit google maps. Sign up for "new maps". Visit somewhere on the map and zoom all the way in then zoom in and out a bit. I have triggered this bug a few times just by doing that. I'm not using dual screens or anything funky. Just a basic Ubuntu 13.10 install with Unity.
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : | #162 |
Forgot to mention, I am using the semaphores kernel parameter...
alan@wopr:~$ cat /proc/cmdline
BOOT_IMAGE=
Lorant Nemeth (loci) wrote : Re: [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 | #163 |
Hi,
I can confirm, that this way I'm able to reproduce the bug as well.
Br,
Loci
On 09/11/2013 03:02 AM, Alan Pope ㋛ wrote:
> I filed the duplicate of this bug 1222261 as I get this frequently on
> both my i7 laptop and i7 desktop.
>
> I think I found a way to reproduce it easily on demand. Open chromium,
> and visit google maps. Sign up for "new maps". Visit somewhere on the
> map and zoom all the way in then zoom in and out a bit. I have triggered
> this bug a few times just by doing that. I'm not using dual screens or
> anything funky. Just a basic Ubuntu 13.10 install with Unity.
>
bharath (bharath1097) wrote : | #164 |
(In reply to #163)
I can reproduce this bug as well on a sandybridge i5 desktop
mike@papersolve.com (mike-papersolve) wrote : | #165 |
I can also reproduce the bug using the new Google Maps (easiest way to do so seems to be zooming in/out). However it occurs for me even after I disable semaphores:
root@hawty:~# cat /sys/module/
0
(after that):
[614445.590357] [drm:i915_
[614445.590468] [drm:i915_
this is ubuntu 13.04 with 2.21.6-0ubuntu4 intel driver, but kernel 3.11.1.
Chris Wilson (ickle) wrote : | #166 |
That's because that would be NOT the same bug.
mike@papersolve.com (mike-papersolve) wrote : | #167 |
Sorry. :) Unfortunately/
In freedesktop.org Bugzilla #54226, Yjcoshc (yjcoshc) wrote : | #168 |
Created attachment 87101
i915_error_state (kernel 3.11.3)
In freedesktop.org Bugzilla #54226, Yjcoshc (yjcoshc) wrote : | #169 |
After playing hedgewars for about half an hour, the gpu started to hang.
dmesg output:
[ 3442.907459] [drm:i915_
[ 3442.907471] [drm] capturing error event; look for more information in /sys/kernel/
[ 3442.916792] [drm:i915_
[ 3466.911077] [drm:i915_
[ 3466.911087] [drm:i915_
[ 3466.947069] [drm:__
I'm not sure my problem is related to this bug.
In freedesktop.org Bugzilla #54226, Yjcoshc (yjcoshc) wrote : | #170 |
(In reply to comment #104)
> After playing hedgewars for about half an hour, the gpu started to hang.
> dmesg output:
> [ 3442.907459] [drm:i915_
> [ 3442.907471] [drm] capturing error event; look for more information in
> /sys/kernel/
> [ 3442.916792] [drm:i915_
> bo (0x5e52000 ctx 1) at 0x5e52220
> [ 3466.911077] [drm:i915_
> [ 3466.911087] [drm:i915_
> [ 3466.947069] [drm:__
> forcewake old ack to clear.
> I'm not sure my problem is related to this bug.
My laptop is Thinkpad T420 with i5-2520M. The BIOS version is 1.44.
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #171 |
(In reply to comment #104)
> I'm not sure my problem is related to this bug.
Most likely it isn't - gpu hang is similar to an application crashing. Please file a new bug report and don't forget to attach the error state file. That's the first thing we need to triage the bug.
And of course list the versions of all the userspace driver parts (mesa, ddx, ...) since like a normal application crash most often it's not a kernel bug, but a bug in the render commands submitted by userspace to the gpu.
In freedesktop.org Bugzilla #54226, Longerdev (longerdev) wrote : | #172 |
(In reply to comment #106)
> (In reply to comment #104)
> > I'm not sure my problem is related to this bug.
>
> Most likely it isn't - gpu hang is similar to an application crashing.
> Please file a new bug report and don't forget to attach the error state
> file. That's the first thing we need to triage the bug.
>
> And of course list the versions of all the userspace driver parts (mesa,
> ddx, ...) since like a normal application crash most often it's not a kernel
> bug, but a bug in the render commands submitted by userspace to the gpu.
Why userspace drivers can breaking render and calling error in kernel part of driver? May be can add "filter" sent commands and ignore (or other reaction, but not execute their) their?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #173 |
(In reply to comment #107)
> (In reply to comment #106)
> > (In reply to comment #104)
> > > I'm not sure my problem is related to this bug.
> >
> > Most likely it isn't - gpu hang is similar to an application crashing.
> > Please file a new bug report and don't forget to attach the error state
> > file. That's the first thing we need to triage the bug.
> >
> > And of course list the versions of all the userspace driver parts (mesa,
> > ddx, ...) since like a normal application crash most often it's not a kernel
> > bug, but a bug in the render commands submitted by userspace to the gpu.
>
> Why userspace drivers can breaking render and calling error in kernel part
> of driver? May be can add "filter" sent commands and ignore (or other
> reaction, but not execute their) their?
The GPU is a full Turing complete computational engine (in fact, lots of them coupled in parallel and in series), see http://
Shuhao (shuhao) wrote : | #174 |
Does anyone here notice graphics slow down? After a couple minutes of game play with CSS, my framerate would drop to about 20fps (status of other activities on the computer will also slowdown).
This did not happen in 13.04 but is occuring with 13.10.
In freedesktop.org Bugzilla #54226, Yjcoshc (yjcoshc) wrote : | #175 |
(In reply to comment #106)
> (In reply to comment #104)
> > I'm not sure my problem is related to this bug.
>
> Most likely it isn't - gpu hang is similar to an application crashing.
> Please file a new bug report and don't forget to attach the error state
> file. That's the first thing we need to triage the bug.
>
> And of course list the versions of all the userspace driver parts (mesa,
> ddx, ...) since like a normal application crash most often it's not a kernel
> bug, but a bug in the render commands submitted by userspace to the gpu.
Someone has reported it here.
https:/
In freedesktop.org Bugzilla #54226, Honza-h (honza-h) wrote : | #176 |
Hello. Same problem here.
[ 485.443455] [drm:i915_
[ 485.443467] [drm] capturing error event; look for more information in /sys/kernel/
[ 485.452727] [drm:i915_
[ 821.726799] [drm:i915_
[ 821.726873] [drm:i915_
[ 1311.134514] [drm:i915_
[ 1311.134613] [drm:i915_
sys: fedora 19 64b
Linux jarvis 3.11.2-
WM: KDE with effects enabled
8G ram
300G SATA HDD
ntb Lenovo ThinkPad E320
problem occurs in:
- scrolling in firefox
- playing video in vlc and switch to KDE terminal or another app
- sometimes system hangs, cpu 100%, freeze and hard reboot needed
- sometimes happens if I work with ff or in terminal only (very frustrating)
- happening across many kernel versions 3.0 to newest I think
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
03:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
08:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #177 |
(In reply to comment #110)
> Hello. Same problem here.
>
> [ 485.443455] [drm:i915_
> [ 485.443467] [drm] capturing error event; look for more information in
> /sys/kernel/
> [ 485.452727] [drm:i915_
> bo (0xa637000 ctx 1) at 0xa6371c8
Unlikey that this is the same gpu hang. Please file a new bug report and attach the error state.
In freedesktop.org Bugzilla #54226, theghost (theghost) wrote : | #178 |
Just a few remarks.
I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904.
Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups highly increased (especially in games).
Additionally with running the latest drivers complete system lockups are gone, but it's still a lockup for multiple seconds with following VT switching.
Maybe these observations help somehow.
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #179 |
(In reply to comment #112)
> Just a few remarks.
> I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904.
> Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups
> highly increased (especially in games).
On snb the blorp engine in mesa has become a bit more hang-happy, see bug #70151
Not all gpu hangs are created equal ;-)
> Additionally with running the latest drivers complete system lockups are
> gone, but it's still a lockup for multiple seconds with following VT
> switching.
You mean a gpu hang happens while when doing a vt switch?
In freedesktop.org Bugzilla #54226, theghost (theghost) wrote : | #180 |
(In reply to comment #113)
> On snb the blorp engine in mesa has become a bit more hang-happy, see bug
> #70151
> Not all gpu hangs are created equal ;-)
>
Actually it was on Sandybridge.
> You mean a gpu hang happens while when doing a vt switch?
No I meant, if you suffer a lockup you just have to wait a few seconds and switch to another VT and back, then you can resume with your system (although sometimes fonts are broken).
In freedesktop.org Bugzilla #54226, Alexander (bay-hackerdom) wrote : | #181 |
Created attachment 87857
i915_error_state
I also met this bug while I was watching video in mplayer. It every 1-2 hours.
[40787.765816] [drm:i915_
[40787.765852] [drm] capturing error event; look for more information in /sys/kernel/
[40787.772361] [drm:i915_
In freedesktop.org Bugzilla #54226, Alexander (bay-hackerdom) wrote : | #182 |
Created attachment 87858
X -version output
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #183 |
(In reply to comment #115)
> Created attachment 87857 [details]
> i915_error_state
>
> I also met this bug while I was watching video in mplayer. It every 1-2
> hours.
>
> [40787.765816] [drm:i915_
> [40787.765852] [drm] capturing error event; look for more information in
> /sys/kernel/
> [40787.772361] [drm:i915_
> bo (0x1fb63000 ctx 1) at 0x1fb63220
This looks like bug #70151, but is definitely not this bug here.
Thomas Mayer (thomas303) wrote : | #184 |
It seems that ubuntu 12.04.3 is also affected.
I get the error using ubuntu 12.04.3 (after upgrading from 12.04.2 in the last days):
Oct 28 18:43:29 localhost kernel: [31236.041655] [drm:i915_
Oct 28 18:43:29 localhost kernel: [31236.041664] [drm] capturing error event; look for more information in /debug/
Oct 28 18:43:32 localhost kernel: [31239.040790] [drm:i915_
Oct 28 18:43:32 localhost kernel: [31239.041127] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Oct 28 18:43:32 localhost kernel: [31239.041132] [drm:i915_reset] *ERROR* Failed to reset chip.
Oct 28 18:43:38 localhost gnome-session[
Oct 28 18:43:38 localhost gnome-session[
Kernel version:
3.8.0-32-generic #47~precise1-Ubuntu SMP Wed Oct 2 16:19:35 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
xserver-
For me the error occurs when I move the mouse cursor in the PhpStorm IDE, which is based on oracle java (I use version 1.8). The error occurs every few hours when working with PhpStorm 7.0
theghost (theghost) wrote : | #185 |
@thomas303: Since 12.04.3 uses the video stack and kernel of Raring it's no wonder that it's also affected.
If you didn't have the errors before 12.04.3 you can still revert to the video stack / kernel of 12.04.2 (Quantal) or 12.04 (Precise).
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : | #186 |
I have been running kernel 3.12.0-
theghost (theghost) wrote : | #187 |
@popey:
I tested kernel 3.12.0-
[ 2937.818867] [drm:i915_
[ 2943.810157] [drm] stuck on render ring
[ 2943.810208] [drm:i915_
[ 3152.914976] [drm] stuck on render ring
[ 3152.915045] [drm:i915_
[ 3568.158967] [drm] stuck on render ring
[ 3568.174992] [drm:i915_
[ 3568.175030] [drm:i915_
[ 3839.310462] [drm] stuck on render ring
[ 3839.310463] [drm] stuck on blitter ring
[ 4292.575683] [drm] stuck on render ring
[ 4292.575684] [drm] stuck on blitter ring
So it's still in the kernel. ;)
In freedesktop.org Bugzilla #54226, Yjcoshc (yjcoshc) wrote : | #188 |
Created attachment 89314
i915_error_state (kernel 3.11.6, mesa 9.2.2, xf86-video-intel 2.99.906)
GPU hangs after playing hedgewars for a few minutes. Thinkpad T420 laptop, i5-2520M.
dmesg error message:
[16901.286432] [drm:i915_
[16901.286441] [drm:i915_
[16901.286444] [drm] capturing error event; look for more information in /sys/kernel/
[16908.287504] [drm:i915_
[16908.287508] [drm:i915_
theghost (theghost) wrote : | #189 |
If you have these problems running Dota 2, you should try Mesa Git or wait for Mesa 10. It contains several patches to remove lockups.
For me on Dota 2 the lockups are completely gone, probably they're also gone in other applications.
In freedesktop.org Bugzilla #54226, Kenxeth (kenxeth) wrote : | #190 |
*** Bug 71890 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #191 |
*** Bug 72048 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #192 |
*** Bug 72829 has been marked as a duplicate of this bug. ***
penalvch (penalvch) wrote : | #193 |
Rocko, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-
apport-collect -p linux REPLACE-
Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.
If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https:/
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags:
kernel-
kernel-
As well, please remove the tag:
needs-upstream-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.
description: | updated |
tags: | added: bios-outdated-a12 |
Changed in linux (Ubuntu): | |
importance: | High → Low |
status: | Confirmed → Incomplete |
tags: | added: needs-upstream-testing regression-potential |
Hamish MacEwan (hamish-macewan) wrote : Re: [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 | #194 |
On 8 January 2014 07:20, Christopher M. Penalver
<email address hidden> wrote:
> Rocko, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO images are available from http://
> /daily-
Hi Christopher, I'm not Rocko, but haven't had any trouble with this
bug on Debian of late.
Hamish.
--
http://
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #195 |
*** Bug 73659 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, A-bugzilla (a-bugzilla) wrote : | #196 |
Created attachment 92710
i915_error_state
I'm also getting regular Sandybridge GPU lockups with Mesa 10.0.1 and Linux kernel 3.13.
dmesg output:
[ 918.876872] [drm] stuck on render ring
[ 918.876876] [drm] stuck on blitter ring
[ 918.876878] [drm] GPU crash dump saved to /sys/class/
[ 918.876879] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 918.876879] [drm] Please file a _new_ bug report on bugs.freedeskto
[ 918.876880] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 918.876880] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 932.923240] [drm] stuck on render ring
[ 932.923242] [drm] stuck on blitter ring
Unfortunately the crash dump doesn't help - it's an empty file!
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #197 |
*** Bug 74180 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #198 |
*** Bug 74265 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #199 |
*** Bug 74452 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #200 |
*** Bug 74473 has been marked as a duplicate of this bug. ***
Adam Conrad (adconrad) wrote : | #201 |
This is still happening (although very infrequently) on current trusty. I just hit it this morning.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #202 |
*** Bug 74867 has been marked as a duplicate of this bug. ***
Steven Goris (sg-steven13) wrote : | #203 |
I experience this bug on Linux Mint 16 Cinnamon. It drives me crazy. My computer hangs approx every 2 hours. I tried the fix in grub. I hope it works as a temporary fix, because I can't work like this on my computer.
Linux 3.11.0-15-generic
no longer affects: | linuxmint |
unksi (unksi) wrote : | #204 |
I found it a big help to switch to tty1 with ctrl+alt+F1 and then back with ctrl+alt+F7/F8. This would make it return to normal a lot faster, and unstuck it most of the times it seems to be totally stuck.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #205 |
*** Bug 75163 has been marked as a duplicate of this bug. ***
Spect (al106208) wrote : | #206 |
I experience this bug on Ubuntu 12.04.4.
System: Ubuntu 12.04.4 LTS x86_64
Kernel: 3.11.0-17-generic DE: Unity Session: ubuntu
Use: xserver-
-------
Processor: Intel(R) Core(TM) i3-2100T CPU @ 2.50GHz Memory (Gb): 7.53
Video: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Gigabyte Technology Co., Ltd Device d000 Kernel driver in use: i915
-------
kern.log:
Feb 28 15:24:44 specttop kernel: [42677.565850] [drm:i915_
Feb 28 15:24:44 specttop kernel: [42677.565904] [drm:i915_
In freedesktop.org Bugzilla #54226, Simtn (simtn) wrote : | #207 |
Created attachment 95090
Another version of the same hang - directed here from bug 75502
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #208 |
*** Bug 75999 has been marked as a duplicate of this bug. ***
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → In Progress |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #209 |
*** Bug 76408 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #210 |
*** Bug 76677 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #211 |
*** Bug 76801 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Phil Turmel (pturmel-lp) wrote : | #212 |
For what its worth, running 3.13.7 greatly mitigates this bug, to where the dead time is barely noticeable. It happened three times in short order here and I didn't notice any of them:
[ 4562.551141] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4582.530028] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4633.476199] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #213 |
*** Bug 77043 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #214 |
*** Bug 77058 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Phil Turmel (pturmel-lp) wrote : | #215 |
My stuck ring faults are completely gone with i915.i915_
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #216 |
Oh that's interesting. We might be able to find a register to prevent rc6 whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just frob forcewake directly.)
In freedesktop.org Bugzilla #54226, Phil Turmel (pturmel-lp) wrote : | #217 |
(In reply to comment #139)
> Oh that's interesting. We might be able to find a register to prevent rc6
> whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just
> frob forcewake directly.)
Happy to test patches. I'm updating to 3.13.9 tonight. I could add something on top if you have ideas. If you need more info than my attachment to #76801 just let me know.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #218 |
*** Bug 77147 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #219 |
*** Bug 77974 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #220 |
*** Bug 78317 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Hoek (artjom-simon) wrote : | #221 |
Created attachment 98589
Kernel 3.14.2-1-ARCH, xf86-video-intel 2.99.911-2, mesa 10.1.2-1
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #222 |
*** Bug 78785 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #223 |
*** Bug 79500 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #224 |
*** Bug 79640 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Jani-nikula (jani-nikula) wrote : | #225 |
commit ca79d888eb63cda
Author: Chris Wilson <email address hidden>
Date: Fri Jun 6 10:22:29 2014 +0100
drm/i915: Reorder semaphore deadlock check
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #226 |
*** Bug 80055 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #227 |
*** Bug 80125 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #228 |
*** Bug 80168 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #229 |
*** Bug 80401 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #230 |
*** Bug 80592 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #231 |
*** Bug 80935 has been marked as a duplicate of this bug. ***
DooMMasteR (winrootkit) wrote : | #232 |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #233 |
*** Bug 81064 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Kurt Roeckx (kurt-roeckx) wrote : | #234 |
Can someone indicate what the current status of this is?
In freedesktop.org Bugzilla #54226, Yunloh (yunloh) wrote : | #235 |
I haven't seen it with xorg-x11-
In freedesktop.org Bugzilla #54226, Kurt Roeckx (kurt-roeckx) wrote : | #236 |
I'm using 2.21.15 which as far as I know is the latest release.
In freedesktop.org Bugzilla #54226, Andre Robatino (robatino) wrote : | #237 |
I am seeing
[drm:i915_
followed by a graphics freeze and the need to reboot (if I can) in Fedora 20 with the latest updates including the 3.15.4 kernel.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #238 |
*** Bug 81402 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Matteo Croce (teknoraver) wrote : | #239 |
same happens with 3.15.0 on Ubuntu 14.04 64 bit
Jul 11 12:43:41 localhost kernel: [42049.462542] [drm] stuck on render ring
Jul 11 12:43:41 localhost kernel: [42049.463330] [drm] GPU HANG: ecode 0:0x00ffffff, in chrome [2172], reason: Ring hung, action: reset
Jul 11 12:43:41 localhost kernel: [42049.463334] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jul 11 12:43:41 localhost kernel: [42049.463335] [drm] Please file a _new_ bug report on bugs.freedeskto
Jul 11 12:43:41 localhost kernel: [42049.463336] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jul 11 12:43:41 localhost kernel: [42049.463337] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jul 11 12:43:41 localhost kernel: [42049.463338] [drm] GPU crash dump saved to /sys/class/
Jul 11 12:43:43 localhost kernel: [42051.464623] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Jul 11 12:43:47 localhost kernel: [42055.468816] [drm] stuck on render ring
Jul 11 12:43:47 localhost kernel: [42055.469614] [drm] GPU HANG: ecode 0:0x00ffffff, in chrome [2172], reason: Ring hung, action: reset
Jul 11 12:43:49 localhost kernel: [42057.470899] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Jul 11 12:43:53 localhost kernel: [42061.439056] [drm] stuck on render ring
Jul 11 12:43:53 localhost kernel: [42061.439867] [drm] GPU HANG: ecode 0:0xfeffffff, in chrome [2172], reason: Ring hung, action: reset
In freedesktop.org Bugzilla #54226, Cwawak (cwawak) wrote : | #240 |
[872948.822279] [drm] stuck on render ring
[872948.822291] [drm] stuck on blitter ring
[872948.823041] [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [30647], reason: Ring hung, action: reset
[872948.823045] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[872948.823046] [drm] Please file a _new_ bug report on bugs.freedeskto
[872948.823047] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[872948.823048] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[872948.823049] [drm] GPU crash dump saved to /sys/class/
[872948.823168] [drm:i915_
[872950.821912] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Linux bobloblaw 3.15.0-
Attaching gpu crash dump as card0-error.
In freedesktop.org Bugzilla #54226, Cwawak (cwawak) wrote : | #241 |
Created attachment 102991
card0-error.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #242 |
*** Bug 81673 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #243 |
*** Bug 81676 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #244 |
*** Bug 81710 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #245 |
*** Bug 81844 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #246 |
*** Bug 81990 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #247 |
*** Bug 82277 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #248 |
*** Bug 82301 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #249 |
*** Bug 82399 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #250 |
*** Bug 82451 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Mstahl (mstahl) wrote : | #251 |
*** Bug 82620 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #252 |
*** Bug 82631 has been marked as a duplicate of this bug. ***
Changed in xserver-xorg-video-intel (Ubuntu): | |
assignee: | Timo Aaltonen (tjaalton) → nobody |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #253 |
*** Bug 82666 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #254 |
*** Bug 82691 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #255 |
*** Bug 82901 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #256 |
*** Bug 83098 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #257 |
*** Bug 83156 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #258 |
*** Bug 83326 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #259 |
*** Bug 83473 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #260 |
*** Bug 83661 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Manuel Widmer (m-widmer-d) wrote : | #261 |
Is there any ongoing development to fix this bug? I still see it with
Linux <hostname> 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
And the latest intel drivers as provided by intel linux graphics installer from
https:/
Many times my system freezes few minutes after starting to watch a movie with vlc. I have my screen connected through a receiver (hdmi for audio + video) with the linux system. The probability for a freeze is higher when the hdmi receiver was powered of for some time before playing the movie than when I do a reboot and hdmi is always on.
I'm happy to help with crashdumps as far as I'm able to collect them.
In freedesktop.org Bugzilla #54226, Bartosz Brachaczek (b-brachaczek) wrote : | #262 |
(In reply to comment #183)
I recommend configuring i915.semaphores=0. I did it and it doesn't freeze anymore.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #263 |
*** Bug 83721 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #264 |
*** Bug 83783 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Frank Stephan (f-st) wrote : | #265 |
Hi Chris,
meanwhile my current kernel is 3.16.1-
I'm wondering (after a reinstall) that the semaphore bug hasn't occured yet, which was the case before (after a fresh install).
This leads me to 4 definable possible reasons:
1. the named kernel revision somehow contains a fix for it. looking at the changes I could'nt get an affirmation to that assumption.
2. cgroup_
3. the BIOS settings (which could be different now) might have something to do with it.
4. I haven't installed KVM suppport yet.
I'll post again if I find a reproducible explanation.
Frank
In freedesktop.org Bugzilla #54226, Frank Stephan (f-st) wrote : | #266 |
2. of course I meant cgroup_
In freedesktop.org Bugzilla #54226, Frank Stephan (f-st) wrote : | #267 |
Hi Chris,
OK, nothing of the above was the reason. In my case it's simply this:
/etc/X11/
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection
I added it when the tearing scrolling through large webpages annoyed me.
As soon as I added it, the problems quickly started.
Selfmade problem.
Frank
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #268 |
(In reply to comment #189)
> Hi Chris,
>
> OK, nothing of the above was the reason. In my case it's simply this:
>
> /etc/X11/
>
> Section "Device"
> Identifier "Intel Graphics"
> Driver "intel"
> Option "TearFree" "true"
> EndSection
>
>
> I added it when the tearing scrolling through large webpages annoyed me.
> As soon as I added it, the problems quickly started.
>
> Selfmade problem.
Not really, https:/
If you want to experiment:
http://
should have an interesting fix, at least for trying to prevent the TearFree leading to the semaphore hang.
In freedesktop.org Bugzilla #54226, Arrowsmith (arrowsmith) wrote : | #269 |
What information is most useful for these repeating issues, as it just happened again:
Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on render ring
Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on blitter ring
Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.140239] [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [26353], reason: Ring hung, action: reset
Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.140750] [drm:i915_
Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] stuck on render ring
Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] stuck on blitter ring
Sep 16 08:32:59 arrowsmithlap1 kernel: [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [26353], reason: Ring hung, action: reset
Sep 16 08:32:59 arrowsmithlap1 kernel: [drm:i915_
Sep 16 08:33:01 arrowsmithlap1 kernel: [1182244.142445] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Sep 16 08:33:01 arrowsmithlap1 kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
The only thing under my /etc/X11/
Do you want a copy of /sys/class/
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #270 |
(In reply to comment #191)
> What information is most useful for these repeating issues, as it just
> happened again:
>
> Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on
> render ring
> Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on
> blitter ring
So long as it is the same event, there is no more information we need other than testing feedback for an eventual workaround.
In freedesktop.org Bugzilla #54226, Manuel Widmer (m-widmer-d) wrote : | #271 |
(In reply to comment #184)
> (In reply to comment #183)
>
> I recommend configuring i915.semaphores=0. I did it and it doesn't freeze
> anymore.
Meanwhile I tested both i915.semaphores=0 and i915.semaphores=1 neither of which did help in my case. But with i915.semaphores=0 my system became much more unstable and even crashed on its own after some days without stress on graphics (just ran some desktop apps like thunar or vlc for music only - no movies). With i915.semaphores=1 the system is at least stable (for some weeks) as long as I don't heavily use desktop applications.
In freedesktop.org Bugzilla #54226, Mika-kuoppala (mika-kuoppala) wrote : | #272 |
*** Bug 85194 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #273 |
*** Bug 85333 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #274 |
*** Bug 85609 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Josh Glover (jmglov) wrote : | #275 |
I am also experiencing this, on a Gentoo system running on a ThinkPad T440s. I'm not doing anything related to XBMC, simply using xrandr for multihead. The interesting thing is that DRI works fine on my laptop screen (glxgears reports 60fps, which is the refresh rate of my screen), but breaks when I move a window trying to use DRI (e.g. Chrome, glxgears) to the external monitor connected to the mini Display Port output.
I see this stuff in dmesg:
[ 3561.424762] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring
[ 3561.424770] [drm] GPU crash dump saved to /sys/class/
[ 3561.424772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 3561.424774] [drm] Please file a _new_ bug report on bugs.freedeskto
[ 3561.424776] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 3561.424778] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 3566.422957] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring
[ 3571.425143] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring
[ 3575.423680] [drm:ring_stuck] *ERROR* Kicking stuck wait on blitter ring
Seems like the same issue. I'm trying to downgrade X, mesa, et al., to try and get the system back in working order.
In freedesktop.org Bugzilla #54226, Daniel-ffwll (daniel-ffwll) wrote : | #276 |
*** Bug 79675 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #277 |
*** Bug 85972 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #278 |
*** Bug 86058 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Fritsch-b (fritsch-b) wrote : | #279 |
For those running Ubuntu, here is a build of a kernel based on 3.17.1 with the patches Chris Willson wants you to test:
- Those patches have other regressions (so be careful to only test your specific issue).
https:/
https:/
Those kernels are based on: https:/
Beware, don't switch VTs.
In freedesktop.org Bugzilla #54226, Tomas Huryn (thuryn1) wrote : | #280 |
I've tryed the mentioned kernel on my Fedora 21 Beta and still hangs after for example Netbeans opens main window for the whole screen.
In freedesktop.org Bugzilla #54226, Smruti-patil (smruti-patil) wrote : | #281 |
*** Bug 86437 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #282 |
*** Bug 86765 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #283 |
*** Bug 86836 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #284 |
*** Bug 86925 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #285 |
*** Bug 87710 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #286 |
*** Bug 87776 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #287 |
*** Bug 88541 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Samuel Rakitničan (semirocket) wrote : | #288 |
*** Bug 88626 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #289 |
*** Bug 88723 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #290 |
*** Bug 88789 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #291 |
*** Bug 89078 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #292 |
*** Bug 89299 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #293 |
*** Bug 89570 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #294 |
*** Bug 89671 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #295 |
*** Bug 89774 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #296 |
*** Bug 89771 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #297 |
*** Bug 89981 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #298 |
*** Bug 90106 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #299 |
*** Bug 90146 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #300 |
*** Bug 90271 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #301 |
*** Bug 90473 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #302 |
*** Bug 90835 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, helios (martin-lichtvoll) wrote : | #303 |
Chris, you referred me to this bug as I reported
Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x00000000, Kicking stuck semaphore on render ring
I skimmed through it and it appears that there are some patches to test? But I am not sure which ones these are. Can you or someone else enlighten me?
Also I note that I still use
Option "AccelMethod" "uxa"
and I have
martin@merkaba:~> cat /etc/modprobe.
options i915 modeset=1 i915_enable_rc6=7
thus maximum energy saving. But according to powertop it never enters the highest sleep state anyway.
I will remove the AccelMethod setting now and see whether it helps. If not, I downgrade to 4.1-rc4 for now, as issues have been at least much less frequent with it.
And its really that for me 4.1-rc6 makes things much *worse*. I am typing this after a clean reboot and already got the GPU hang again. It happens about every few minutes. Are you really sure this is the same GPU hang? I didn´t have this before 4.1 kernel?
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #304 |
(In reply to Martin Steigerwald from comment #225)
> Chris, you referred me to this bug as I reported
>
> Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x00000000, Kicking stuck
> semaphore on render ring
>
> I skimmed through it and it appears that there are some patches to test? But
> I am not sure which ones these are. Can you or someone else enlighten me?
There's likely a modest improvement in 4.2.
> Also I note that I still use
>
> Option "AccelMethod" "uxa"
>
> and I have
>
> martin@merkaba:~> cat /etc/modprobe.
> options i915 modeset=1 i915_enable_rc6=7
Fortuitously that dangerous option doesn't do anything for your kernel.
> ffffffff813a4b0e
> thus maximum energy saving. But according to powertop it never enters the
> highest sleep state anyway.
>
> I will remove the AccelMethod setting now and see whether it helps. If not,
> I downgrade to 4.1-rc4 for now, as issues have been at least much less
> frequent with it.
Purely circumstantial.
> And its really that for me 4.1-rc6 makes things much *worse*. I am typing
> this after a clean reboot and already got the GPU hang again. It happens
> about every few minutes. Are you really sure this is the same GPU hang? I
> didn´t have this before 4.1 kernel?
Yes.
In freedesktop.org Bugzilla #54226, helios (martin-lichtvoll) wrote : | #305 |
(In reply to Chris Wilson from comment #226)
> (In reply to Martin Steigerwald from comment #225)
> > Chris, you referred me to this bug as I reported
> >
> > Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x00000000, Kicking stuck
> > semaphore on render ring
> >
> > I skimmed through it and it appears that there are some patches to test? But
> > I am not sure which ones these are. Can you or someone else enlighten me?
>
> There's likely a modest improvement in 4.2.
Nice.
> > Also I note that I still use
> >
> > Option "AccelMethod" "uxa"
> >
> > and I have
> >
> > martin@merkaba:~> cat /etc/modprobe.
> > options i915 modeset=1 i915_enable_rc6=7
>
> Fortuitously that dangerous option doesn't do anything for your kernel.
Well I found out why, I compiled i915 into the kernel it seems, at least I don´t have an i915 module in lsmod. But also i915.i915_
> > ffffffff813a4b0e
> > thus maximum energy saving. But according to powertop it never enters the
> > highest sleep state anyway.
> >
> > I will remove the AccelMethod setting now and see whether it helps. If not,
> > I downgrade to 4.1-rc4 for now, as issues have been at least much less
> > frequent with it.
>
> Purely circumstantial.
Since using SNA I didn´t see a GPU hang so far. Too early to say for sure, but it seems something in UXA may have triggered it more easily.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #306 |
*** Bug 91212 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #307 |
*** Bug 91662 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #308 |
*** Bug 91810 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #309 |
*** Bug 91832 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Samuel Rakitničan (semirocket) wrote : | #310 |
(In reply to Chris Wilson from comment #192)
> (In reply to comment #191)
> > What information is most useful for these repeating issues, as it just
> > happened again:
> >
> > Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on
> > render ring
> > Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on
> > blitter ring
>
> So long as it is the same event, there is no more information we need other
> than testing feedback for an eventual workaround.
Is this the same bug?
$ journalctl -p 3 -b -1
Ruj 25 02:13:01 crnigrom kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
Ruj 25 02:13:01 crnigrom kernel: [drm:__
... [ repeated messages ] ...
Ruj 25 02:13:33 crnigrom kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
Ruj 25 02:13:33 crnigrom kernel: [drm:__
Ruj 25 02:13:34 crnigrom kernel: [drm:stop_ring [i915]] *ERROR* render ring : timed out trying to stop ring
Ruj 25 02:13:34 crnigrom kernel: [drm:init_
Ruj 25 02:13:34 crnigrom kernel: [drm:i915_reset [i915]] *ERROR* Failed hw init on reset -5
Ruj 25 02:13:34 crnigrom gnome-session[
After which gnome crashes with "Oh No Something Is Wrong" screen
$ uname -r
4.1.7-200.
Hardware i3-2100 CPU/GPU
This bug is going on already for a long long time, but at least computer is not hard freezing anymore, although gnome is crashing so any gtk applications running doing something stalls.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #311 |
*** Bug 92118 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #312 |
*** Bug 92739 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Arrowsmith (arrowsmith) wrote : | #313 |
FWIW, my issue (https:/
HTH someone.
In freedesktop.org Bugzilla #54226, Jefbed (jefbed) wrote : | #314 |
Created attachment 119432
attachment-
I reported this bug from a system without an SSD. Recently, I have not
seen the kernel messages appear however--currently on linux 4.2.5.
On Sun, Nov 1, 2015 at 10:04 PM, <email address hidden> wrote:
> *Comment # 235 <https:/
> on bug 54226 <https:/
> <email address hidden> <email address hidden> *
>
> FWIW, my issue (https:/
> resolved by uninstalling various components, re-installing and updating them. I
> have a hunch (completely unproven) that it was a transparent bit-fail issue
> from the SSD. By un-installing and re-installing, the files were likely
> installed to a different location on the drive. It wasn't configuration, as I
> tried erasing, and even rolling back to defaults, with the problem still
> persisting. As it was almost daily, prior to uninstall, and hasn't happened
> since the install, this is all I can attribute it to.
>
> HTH someone.
>
> -------
> You are receiving this mail because:
>
> - You are on the CC list for the bug.
>
>
In freedesktop.org Bugzilla #54226, Arrowsmith (arrowsmith) wrote : | #315 |
(In reply to Jeffrey E. Bedard from comment #236)
> Created attachment 119432 [details]
> attachment-
>
> I reported this bug from a system without an SSD. Recently, I have not
> seen the kernel messages appear however--currently on linux 4.2.5.
Ah, let me clarify that earlier comment: I dd'd a failing spinning drive to an SSD. There was lots of clicking. Upgraded packages as they came in, but no change. Only the uninstall and re-install cleared the repeat button. :)
In freedesktop.org Bugzilla #54226, Jefbed (jefbed) wrote : | #316 |
Created attachment 119433
attachment-
I think this bug can be marked as closed with the latest linux/mesa/xorg
versions :)
On Fri, Nov 6, 2015 at 1:47 AM, <email address hidden> wrote:
> *Comment # 237 <https:/
> on bug 54226 <https:/
> <email address hidden> <email address hidden> *
>
> (In reply to Jeffrey E. Bedard from comment #236 <https:/
> > attachment-
> >
> > I reported this bug from a system without an SSD. Recently, I have not
> > seen the kernel messages appear however--currently on linux 4.2.5.
>
> Ah, let me clarify that earlier comment: I dd'd a failing spinning drive to an
> SSD. There was lots of clicking. Upgraded packages as they came in, but no
> change. Only the uninstall and re-install cleared the repeat button. :)
>
> -------
> You are receiving this mail because:
>
> - You are on the CC list for the bug.
>
>
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #317 |
*** Bug 92927 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #318 |
*** Bug 93057 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Kurt Roeckx (kurt-roeckx) wrote : | #319 |
Created attachment 120189
error state with 4.2 kernel
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #320 |
*** Bug 93331 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #321 |
*** Bug 93482 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #322 |
*** Bug 93493 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #323 |
*** Bug 89524 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #324 |
*** Bug 93595 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #325 |
*** Bug 93876 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #326 |
*** Bug 93824 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #327 |
*** Bug 94057 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, sander eikelenboom (b-linux) wrote : | #328 |
Tuesday, March 1, 2016, 9:43:23 PM, you wrote:
> Chris Wilson changed bug 54226
> WhatRemovedAddedCC <email address hidden>
>
> Comment # 249 on bug 54226 from Chris Wilson
> *** Bug 94057 has been marked as a duplicate of this bug. ***
>
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Sorry to say, but:
Is there a way to get off the CC-list of this slightly depressing kind of "catch-all" bug ?
It unfortunately doesn't seem to have be going anywhere for the last 3 to 4 years accept
for an endless stream of duplicates being appended.
--
Sander
In freedesktop.org Bugzilla #54226, Jani-nikula (jani-nikula) wrote : | #329 |
(In reply to Sander Eikelenboom from comment #250)
> Is there a way to get off the CC-list of this slightly depressing kind of
> "catch-all" bug ?
CC list is at the top right corner. Choose the address, tick "Remove selected CCs", and hit Save Changes.
I've done this for you now.
In freedesktop.org Bugzilla #54226, fjgaude (tanzen) wrote : Re: [Bug 1041790] | #330 |
Please take me off too.
frank
On 03/02/2016 03:33 AM, Jani-nikula wrote:
> (In reply to Sander Eikelenboom from comment #250)
>> Is there a way to get off the CC-list of this slightly depressing kind of
>> "catch-all" bug ?
> CC list is at the top right corner. Choose the address, tick "Remove
> selected CCs", and hit Save Changes.
>
> I've done this for you now.
>
no longer affects: | sandybridge-meta (Ubuntu) |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #331 |
*** Bug 95238 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Samantham (samantham) wrote : | #332 |
Chris, I seem to be experiencing this bug in Linux 4.7rc3 on an x220 ThinkPad with Intel HD 3000 chipset. I was getting random full system freeze, non responsive over network.
The main messages before the crash were:
Jun 23 19:11:18 athena kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
Jun 23 19:11:18 athena kernel: [drm:__
The original crash I haven't been able to reproduce easily but I CAN reproduce every time a full system lockup running the following intel-gpu-tools tests (I have not even close to run all the tests though) [**This may or may not be related to the original crash**]
gem_sync, subtest: bsd2-hang
drv_hangman, subtest: error-state-
I do not know if these tests are helpful or related (maybe some are known to fail? not sure).
I have drm debugging turned on for when I ran those tests. (drm.debug=0x1e log_buf_len=1M)
I can post logs of the hangs associated with the two tests/subtests and run any other tests if you desire (with kernel drm debug on), I will wait for the issue to reappear with the drm debug on before posting that log though. By the number of similar bugs you may already have the CALL TRACE and non-debug level logs.
I know how to patch and am able to compile kernels to test. The bug effects me maybe once every 1 or 2 days. I use XOrg with Glamor. I have been seeing these crashes since 4.6 (maybe 4.5 or earlier not sure).
I know how to apply patches and am able to compile drm-next or any patches you have to see if this issue can be isolated. Thanks, sorry for the long response.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #333 |
*** Bug 97304 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #334 |
*** Bug 97451 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Yann-argotti (yann-argotti) wrote : | #335 |
*** Bug 98294 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #336 |
*** Bug 98807 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #337 |
*** Bug 100245 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Ricardo-vega-u (ricardo-vega-u) wrote : | #338 |
Adding tag into "Whiteboard" field - ReadyForDev
The bug still active
*Status is correct
*Platform is included
*Feature is included
*Priority and Severity correctly set
*Logs included
In freedesktop.org Bugzilla #54226, Samuel Rakitničan (semirocket) wrote : | #339 |
I doesn't seem to be getting mentioned Gnome crashes on my sandybridge anymore with mainline kernels, that is currently 4.11 and I think even with 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default centos 7 kernels I am definitely getting very frequent GPU crashes that brings down Gnome.
So it is either fixed for good, or it become much rarer. The issue I am/was experiencing happens when Gnome is running, it does not happen when only GDM is loaded. System load seems to not have effect on the bug triggering, seems to happen any time, on idle, or when machine is loaded.
In freedesktop.org Bugzilla #54226, Elizabethx-de-la-torre-mena (elizabethx-de-la-torre-mena) wrote : | #340 |
(In reply to samuel.rakitnican from comment #260)
> I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
> anymore with mainline kernels, that is currently 4.11 and I think even with
> 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default
> centos 7 kernels I am definitely getting very frequent GPU crashes that
> brings down Gnome.
>
> So it is either fixed for good, or it become much rarer. The issue I am/was
> experiencing happens when Gnome is running, it does not happen when only GDM
> is loaded. System load seems to not have effect on the bug triggering, seems
> to happen any time, on idle, or when machine is loaded.
Hopefully, is fixed for good. I'm closing this bug, if problem arise with latest kernel versions https:/
Changed in xserver-xorg-video-intel: | |
status: | In Progress → Fix Released |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #341 |
(In reply to Elizabeth from comment #261)
> (In reply to samuel.rakitnican from comment #260)
> > I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
> > anymore with mainline kernels, that is currently 4.11 and I think even with
> > 4.10 I was not getting any issues, with mainline longterm 4.4.61 and default
> > centos 7 kernels I am definitely getting very frequent GPU crashes that
> > brings down Gnome.
> >
> > So it is either fixed for good, or it become much rarer. The issue I am/was
> > experiencing happens when Gnome is running, it does not happen when only GDM
> > is loaded. System load seems to not have effect on the bug triggering, seems
> > to happen any time, on idle, or when machine is loaded.
> Hopefully, is fixed for good. I'm closing this bug, if problem arise with
> latest kernel versions https:/
> and SW information, steps to reproduce and relevant logs.Thank you.
There was no fix for this HW issue.
Changed in xserver-xorg-video-intel: | |
status: | Fix Released → Confirmed |
In freedesktop.org Bugzilla #54226, Aaron-lu-a (aaron-lu-a) wrote : | #342 |
Created attachment 135173
gpu error file on 4.13.5-
This problem reappeared on 4.13.5-
[774249.632109] [drm] GPU HANG: ecode 6:0:0x85fffff8, in Xorg [696], reason: Hang on rcs0, action: reset
[774249.632110] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[774249.632111] [drm] Please file a _new_ bug report on bugs.freedeskto
[774249.632111] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[774249.632111] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[774249.632112] [drm] GPU crash dump saved to /sys/class/
[774249.632172] drm/i915: Resetting chip after gpu hang
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #343 |
commit 0da715ee6077440
Author: Chris Wilson <email address hidden>
Date: Mon Nov 20 20:55:02 2017 +0000
drm/i915: Disable semaphores on Sandybridge
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → Won't Fix |
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #344 |
*** Bug 104243 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #345 |
*** Bug 104304 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #346 |
*** Bug 104772 has been marked as a duplicate of this bug. ***
In freedesktop.org Bugzilla #54226, Jani-saarinen-g (jani-saarinen-g) wrote : | #347 |
I will close this now.
In freedesktop.org Bugzilla #54226, Chris Wilson (ickle) wrote : | #348 |
*** Bug 106119 has been marked as a duplicate of this bug. ***
Status changed to 'Confirmed' because the bug affects multiple users.