From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104817] [Raven][GALLIUM_DDEBUG] system crashes/freezes randomly every few minutes/hours
Date: Sat, 27 Jan 2018 23:04:24 +0000 [thread overview]
Message-ID: <bug-104817-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104817
Bug ID: 104817
Summary: [Raven][GALLIUM_DDEBUG] system crashes/freezes
randomly every few minutes/hours
Product: Mesa
Version: git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: marcus.husar@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 137000
--> https://bugs.freedesktop.org/attachment.cgi?id=137000&action=edit
GALLIUM_DDEBUG: folder ddebug_dumps with multiple dumps
OpenGL renderer string: AMD RAVEN (DRM 3.23.0 / 4.16.0-2.fc27.x86_64, LLVM
6.0.0)
My system is an Acer SF315-41 (Ryzen Mobile 5 2500U) with Fedora 27, Kernel
4.16-drm-next (based on 4.15-rc8), LLVM 6.0.0-rc1, Mesa 18.0.0-rc2.
I can reproduce these crashes from kernel-4.15-rcX/mesa-17.3/llvm5 to
kernel-4.16-drm-next/mesa-18-rc2/llvm6-rc1 and in between. They mostly appear
while watching videos (firefox/totem), switching tabs in firefox, resizing
windows (gnome-shell) or gaming.
With amdgpu.lockup_timeout=2000 and amdgpu.GALLIUM_DDEBUG=2000 I was able to
gather lots of dumps within a few minutes (see attachment). As you can see in
the dumps the GPU lockup results sometimes in a CPU lockup (kernel bluetooth
deadlock) as a result of gnome shell’s complete freezing. I can reproduce
amdgpu crashes also with an USB mouse and bluetooth disabled.
Not very often I can find some kernel errors in the logfiles that result from a
crash. I’ll attach the few I found in the last two weeks.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3432 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-27 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 23:04 bugzilla-daemon [this message]
2018-01-27 23:06 ` [Bug 104817] [Raven][GALLIUM_DDEBUG] system crashes/freezes randomly every few minutes/hours bugzilla-daemon
2018-01-27 23:08 ` bugzilla-daemon
2018-01-27 23:09 ` bugzilla-daemon
2018-04-13 22:27 ` bugzilla-daemon
2018-05-19 4:41 ` bugzilla-daemon
2018-05-19 4:42 ` bugzilla-daemon
2018-07-13 19:58 ` bugzilla-daemon
2018-08-06 10:32 ` bugzilla-daemon
2018-08-06 11:07 ` bugzilla-daemon
2018-08-17 11:34 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104817-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.