Bug 100381 - gnome shell crashing, logs told me to submit here
Summary: gnome shell crashing, logs told me to submit here
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-24 21:33 UTC by Patrick
Modified: 2017-07-25 12:51 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GEM/execlists, GPU hang


Attachments
/sys/class/drm/card0/error (207.51 KB, application/x-lz4)
2017-03-24 21:33 UTC, Patrick
no flags Details

Description Patrick 2017-03-24 21:33:35 UTC
Created attachment 130443 [details]
/sys/class/drm/card0/error

I'm getting regular crashes of gnome-shell under both wayland and xorg. When running under wayland it crashes to the login screen. When running running under xorg it crashes, briefly shows the login screen background image, and reloads with applications as they were.

looking in `journalctl` I find:

[drm] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1819], reason: Hang on render ring, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]
[drm] RC6 on

'/sys/class/drm/card0/error' is attached as error.lz4

This is a nearly fresh install of Fedora 25 with all updates installed. (Re-installed because of this issue assuming it would fix it.) I have not tried compiling a newer version manually yet, but will now look into doing so. (Pointers on where to start with that would be appreciated.)
Comment 1 Chris Wilson 2017-03-24 21:55:39 UTC
It failed between execlists. Can you please try with https://cgit.freedesktop.org/drm-tip as that will capture more information in regards to execlists?
Comment 2 yann 2017-04-11 13:43:38 UTC
(In reply to Chris Wilson from comment #1)
> It failed between execlists. Can you please try with
> https://cgit.freedesktop.org/drm-tip as that will capture more information
> in regards to execlists?

Patrick, any update regarding Chris' demand?
Comment 3 Patrick 2017-04-17 05:42:03 UTC
Sorry, was distracted with a new 3d printer. I finally got it compiled and installed tonight, but I had to go back a few commits to 2ca62d8a606a95e098799f128f6a40a6300d2a2a. Everything after that fails to build for me with:

drivers/gpu/drm/nouveau/nvkm/engine/device/base.c:2347:1: error: redefinition of ‘nv137_chipset’
 nv137_chipset = {
 ^~~~~~~~~~~~~
drivers/gpu/drm/nouveau/nvkm/engine/device/base.c:2290:1: note: previous definition of ‘nv137_chipset’ was here
 nv137_chipset = {
 ^~~~~~~~~~~~~

If being behind is a problem let me know what I can try to fix those errors, otherwise I'll post back once I've seen the problem again.
Comment 4 Jari Tahvanainen 2017-05-23 13:59:03 UTC
Patrick - the problem you are having was a mismerge, and bad timing to have pulled at that moment. So please try again.
Comment 5 Elizabeth 2017-06-23 21:57:07 UTC
(In reply to Jari Tahvanainen from comment #4)
> Patrick - the problem you are having was a mismerge, and bad timing to have
> pulled at that moment. So please try again.

Hello Patrick, 
Is there any update in this case? Have you been able to test it again? Thank you.
Comment 6 Ricardo 2017-07-25 12:50:57 UTC
based on the lack of response from the submitter the bug will be closed, please if you encounter the issue again make sure you open a new bug, but please try it with the latest configuration and attached logs..


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.