Summary: | [skl] GPU HANG: ecode 9:0:0x86dffffd, in X (libreoffice) | ||
---|---|---|---|
Product: | Mesa | Reporter: | adrian.hospodar <adrian.hospodar> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | major | ||
Priority: | medium | CC: | intel-gfx-bugs, mika.kuoppala |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | SKL | i915 features: | GPU hang |
Attachments: |
dmesg
GPU crash dump |
Description
adrian.hospodar@gmail.com
2018-04-24 14:36:11 UTC
What kernel, what system. Have you tried latest drm-tip? https://cgit.freedesktop.org/drm-tip. Also attach the “dmesg” output taken with “drm.debug=0xe” and “log-buf-len=2M” Also attach dmesg from the boot. Created attachment 139060 [details]
dmesg
Created attachment 139061 [details]
GPU crash dump
System linux-bub9:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.3" ID=opensuse ID_LIKE="suse" VERSION_ID="42.3" PRETTY_NAME="openSUSE Leap 42.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" Kernel linux-bub9:~ # uname -a Linux linux-bub9 4.4.126-48-default #1 SMP Sat Apr 7 05:22:50 UTC 2018 (f24992c) x86_64 x86_64 x86_64 GNU/Linux dmesg attached in dmesg.18_32_30 GPU crash in error.gz Rest of info requested on the next crash. Document system: CPU0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (family: 0x6, model: 0x5e, stepping: 0x3) Mika, Chris can you have a look. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1719. |
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.