[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0

[Rocko]

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_LINUX_DEFAULT="quiet splash"

to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

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-xorg-video-intel 2:2.20.3-0ubuntu1
Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
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/apport/apport-gpu-error-intel.py
GpuHangFrequency: Continuously
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
InterpreterPath: /usr/bin/python3.2mu
MachineType: Dell Inc. Dell System XPS L502X
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu3
 libdrm2 2.4.38-0ubuntu2
 xserver-xorg-video-intel 2:2.20.3-0ubuntu1
SourcePackage: xserver-xorg-video-intel
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.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mikhail Gavrilov (mikegav)]

Created attachment 66289
dmesg output

From time to time interface freezes, and in dmesg appear these records: [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer elapsed... blitter ring idle

$ 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)]

Does switching from UXA to SNA help?

[Rocko (rockorequin)]

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)]

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)]

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)]

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/xorg.conf-intel-sna and symlinked to it to test out SNA; then I deleted the symlink, and a day or two later suddenly SNA became the default.

[Rocko (rockorequin)]

Ah, I am using xorg-edgers. Perhaps they are trying out SNA as the default there.

[Rocko (rockorequin)]

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)]

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)]

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)]

Switching from UXA to SNA fixes this for me too, on an Asus Zenbook UX31E

[Dimitri John Ledkov (xnox)]

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)]

@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

[Chris Wilson (ickle)]

If you can easily reproduce this error, can you please build a kernel using http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=xv-overlay which has some revised memory barriers.

[Mikhail Gavrilov (mikegav)]

Can you help me to build rpm for fedora?

[Rocko (rockorequin)]

I still experience this bug, even with the latest intel driver from git, xf86-video-intel-2.6.99.902. I would use SNA but it has an even more annoying bug after the screen saver unlocks where unity just shows me a black screen and mouse cursor, and I have to physically restart unity to get it working again.

[Chris Wilson (ickle)]

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.

[Mikhail Gavrilov (mikegav)]

I am use Fedora 18 with 3.6.7-5.fc18.i686 kernel and in dmesg output still exists message:
[22826.654365] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[22826.654369] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state

[Chris Wilson (ickle)]

That is not the same bug, so you need to attach a fresh set of debug info (please remember the i915_error_state)...

[Mikhail Gavrilov (mikegav)]

Please, explain how get needed debug info. Thanks.

[Chris Wilson (ickle)]

http://intellinuxgraphics.org/how_to_report_bug.html

From which we need the i915_error_state, so

$ sudo mount -tdebugfs debug /sys/kernel/debug
$ sudo cat /sys/kernel/debug/dri/0/i915_error_state > i915_error_state

[Mikhail Gavrilov (mikegav)]

Created attachment 70518
i915_error_state

[Chris Wilson (ickle)]

Looks that corresponds to the bug

commit 1c8b46fc8c865189f562c9ab163d63863759712f
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_REGISTER_IMM command. In cursory testing,
    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://cgit.freedesktop.org/~danvet/drm-intel or available as drm-intel-experimental in the ubuntu kernel-ppa.

[Timo Aaltonen (tjaalton)]

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 :)

[Rocko (rockorequin)]

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)]

@Timo Aaltonen
SNA — ok. looks like some sort of regression in the driver.

[Bryce Harrington (bryce)]

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.

[Mikhail Gavrilov (mikegav)]

Problem repeated with patched kernel.

[118637.439016] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[118637.439020] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[mikhail@localhost ~]$ uname -a
Linux localhost.localdomain 3.6.9-4.1.fc18.i686.PAE #1 SMP Wed Dec 5 15:16:33 UTC 2012 i686 i686 i386 GNU/Linux
[mikhail@localhost ~]$ sudo cat /sys/kernel/debug/dri/0/i915_error_state > i915_error_state
[sudo] password for mikhail:
[mikhail@localhost ~]$

[Mikhail Gavrilov (mikegav)]

Created attachment 71192
i915_error_state (new)

[Mikhail Gavrilov (mikegav)]

sudo cat /sys/kernel/debug/dri/0/i915_error_state > i915_error_state-8
cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory

What it mean??

[Mikhail Gavrilov (mikegav)]

Created attachment 71199
i915_error_state (new)

[Mikhail Gavrilov (mikegav)]

Created attachment 71200
dmesg output (new)

[Chris Wilson (ickle)]

Lalalalala.

[bugbot (bugbot)]

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://cdimage.ubuntu.com/daily-live/
    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://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

[Rocko (rockorequin)]

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.

[Adam Conrad (adconrad)]

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.

[Chris Wilson (ickle)]

*** Bug 91832 has been marked as a duplicate of this bug. ***

[Samuel Rakitničan (semirocket)]

(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:__gen6_gt_wait_for_thread_c0.isra.16 [i915]] *ERROR* GT thread status wait timed out
... [ 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:__gen6_gt_wait_for_thread_c0.isra.16 [i915]] *ERROR* GT thread status wait timed out
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_ring_common [i915]] *ERROR* render ring initialization failed ctl 00000000 (valid? 0) head 00000000 tail 00000000 start 00000000 [expected 00000000]
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[1823]: Unrecoverable failure in required component gnome-shell.desktop

After which gnome crashes with "Oh No Something Is Wrong" screen

$ uname -r
4.1.7-200.fc22.x86_64

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.

[Chris Wilson (ickle)]

*** Bug 92118 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 92739 has been marked as a duplicate of this bug. ***

[Arrowsmith (arrowsmith)]

FWIW, my issue (https://bugs.freedesktop.org/show_bug.cgi?id=54226#c191), was 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.

[Jefbed (jefbed)]

Created attachment 119432
attachment-28908-0.html

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://bugs.freedesktop.org/show_bug.cgi?id=54226#c235>
> on bug 54226 <https://bugs.freedesktop.org/show_bug.cgi?id=54226> from
> <email address hidden> <email address hidden> *
>
> FWIW, my issue (https://bugs.freedesktop.org/show_bug.cgi?id=54226#c191), was
> 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.
>
>

[Arrowsmith (arrowsmith)]

(In reply to Jeffrey E. Bedard from comment #236)
> Created attachment 119432 [details]
> attachment-28908-0.html
>
> 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. :)

[Jefbed (jefbed)]

Created attachment 119433
attachment-32271-0.html

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://bugs.freedesktop.org/show_bug.cgi?id=54226#c237>
> on bug 54226 <https://bugs.freedesktop.org/show_bug.cgi?id=54226> from
> <email address hidden> <email address hidden> *
>
> (In reply to Jeffrey E. Bedard from comment #236 <https://bugs.freedesktop.org/show_bug.cgi?id=54226#c236>)> Created attachment 119432 <https://bugs.freedesktop.org/attachment.cgi?id=119432> [details] <https://bugs.freedesktop.org/attachment.cgi?id=119432&action=edit>
> > attachment-28908-0.html
> >
> > 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.
>
>

[Chris Wilson (ickle)]

*** Bug 92927 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93057 has been marked as a duplicate of this bug. ***

[Kurt Roeckx (kurt-roeckx)]

Created attachment 120189
error state with 4.2 kernel

[Chris Wilson (ickle)]

*** Bug 93331 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93482 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93493 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 89524 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93595 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93876 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 93824 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 94057 has been marked as a duplicate of this bug. ***

[sander eikelenboom (b-linux)]

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

[Jani-nikula (jani-nikula)]

(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.

[fjgaude (tanzen)]

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.
>

[Chris Wilson (ickle)]

*** Bug 95238 has been marked as a duplicate of this bug. ***

[Samantham (samantham)]

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:__gen6_gt_wait_for_thread_c0.isra.7 [i915]] *ERROR* GT thread status wait timed out.

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-capture-bit

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.

[Chris Wilson (ickle)]

*** Bug 97304 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 97451 has been marked as a duplicate of this bug. ***

[Yann-argotti (yann-argotti)]

*** Bug 98294 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 98807 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 100245 has been marked as a duplicate of this bug. ***

[Ricardo-vega-u (ricardo-vega-u)]

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

[Samuel Rakitničan (semirocket)]

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.

[Elizabethx-de-la-torre-mena (elizabethx-de-la-torre-mena)]

(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://www.kernel.org/ please open a NEW bug with HW and SW information, steps to reproduce and relevant logs.Thank you.

[Chris Wilson (ickle)]

(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://www.kernel.org/ please open a NEW bug with HW
> and SW information, steps to reproduce and relevant logs.Thank you.

There was no fix for this HW issue.

[Aaron-lu-a (aaron-lu-a)]

Created attachment 135173
gpu error file on 4.13.5-200.fc26.x86_64

This problem reappeared on 4.13.5-200.fc26.x86_64 last Friday.

[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.freedesktop.org against DRI -> DRM/Intel
[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/drm/card0/error
[774249.632172] drm/i915: Resetting chip after gpu hang

[Chris Wilson (ickle)]

commit 0da715ee60774401bea00dc71fca6fd1096c734a
Author: Chris Wilson <email address hidden>
Date: Mon Nov 20 20:55:02 2017 +0000

    drm/i915: Disable semaphores on Sandybridge

[Chris Wilson (ickle)]

*** Bug 104243 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 104304 has been marked as a duplicate of this bug. ***

[Chris Wilson (ickle)]

*** Bug 104772 has been marked as a duplicate of this bug. ***

[Jani-saarinen-g (jani-saarinen-g)]

I will close this now.

[Chris Wilson (ickle)]

*** Bug 106119 has been marked as a duplicate of this bug. ***