From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205093] New: [amdgpu] resume of IP block <gfx_v8_0> failed -110
Date: Sun, 06 Oct 2019 00:01:47 +0000 [thread overview]
Message-ID: <bug-205093-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205093
Bug ID: 205093
Summary: [amdgpu] resume of IP block <gfx_v8_0> failed -110
Product: Drivers
Version: 2.5
Kernel Version: 5.2.13
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: kat.zygfryd@gmail.com
Regression: No
Created attachment 285359
--> https://bugzilla.kernel.org/attachment.cgi?id=285359&action=edit
Full dmesg on 5.2.13
Once in a while immediately after resuming from suspend the screen freezes for
a moment and then I lose all video signals. System is able to be rebooted with
sysrq.
Hardware:
* Radeon RX 470
* Ryzen 2700
* 64GB ECC RAM
No significant load is put on the GPU, because the system is only used for
work, browsing and playing video.
You can also see bug 202891 (__nvme_disable_io_queues triggers WARNING in
kernel/irq/chip.c:210) in both logs, but that one happens far more often
without this bug comanifesting.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-10-06 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 0:01 bugzilla-daemon [this message]
2019-10-06 0:02 ` [Bug 205093] [amdgpu] resume of IP block <gfx_v8_0> failed -110 bugzilla-daemon
2019-10-06 12:25 ` [Bug 205093] [amdgpu] resume of IP block <gfx_v8_0> failed -110 (GPU crash into black screen) bugzilla-daemon
2019-11-06 11:46 ` bugzilla-daemon
2019-11-08 20:46 ` bugzilla-daemon
2019-11-08 21:10 ` 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-205093-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.