From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108606] Raven Ridge: constant lockups since latest pull from Linus
Date: Tue, 30 Oct 2018 21:41:46 +0000 [thread overview]
Message-ID: <bug-108606-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108606
Bug ID: 108606
Summary: Raven Ridge: constant lockups since latest pull from
Linus
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: samantham@posteo.net
Created attachment 142287
--> https://bugs.freedesktop.org/attachment.cgi?id=142287&action=edit
dmesg log
My system was stable on Linus's branch until he pulled in a bunch of DRM
changes with this merge commit 53b3b6bbfde6. This pull causes the system to
freeze just by using the desktop.
Oct 30 15:31:11 kernel: [drm:gfx_v9_0_priv_reg_irq [amdgpu]] *ERROR* Illegal
register access in command stream
Oct 30 15:31:11 kernel: [drm] GPU recovery disabled.
Oct 30 15:31:22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=61066, emitted seq=61068
Oct 30 15:31:22 kernel: [drm] GPU recovery disabled.
Full dmesg attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2647 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-10-30 21:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 21:41 bugzilla-daemon [this message]
2018-10-30 21:45 ` [Bug 108606] Raven Ridge: constant lockups since latest pull from Linus bugzilla-daemon
2018-10-30 21:50 ` bugzilla-daemon
2018-10-30 22:00 ` bugzilla-daemon
2018-10-31 2:44 ` bugzilla-daemon
2018-10-31 19:07 ` bugzilla-daemon
2018-10-31 19:38 ` bugzilla-daemon
2018-10-31 19:50 ` bugzilla-daemon
2018-10-31 19:52 ` bugzilla-daemon
2018-11-01 2:44 ` bugzilla-daemon
2018-11-01 2:53 ` bugzilla-daemon
2018-11-01 4:27 ` bugzilla-daemon
2018-11-01 5:06 ` bugzilla-daemon
2018-11-01 8:06 ` bugzilla-daemon
2018-11-01 8:21 ` bugzilla-daemon
2018-11-01 16:53 ` bugzilla-daemon
2018-11-01 17:22 ` bugzilla-daemon
2018-11-20 14:46 ` bugzilla-daemon
2018-11-20 14:48 ` bugzilla-daemon
2019-11-19 9:01 ` 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-108606-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.