From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112240] Resume from suspend hangs gfx10 card
Date: Sun, 10 Nov 2019 01:11:04 +0000 [thread overview]
Message-ID: <bug-112240-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1224 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112240
Bug ID: 112240
Summary: Resume from suspend hangs gfx10 card
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: 42.pablo.ms@gmail.com
Created attachment 145929
--> https://bugs.freedesktop.org/attachment.cgi?id=145929&action=edit
Dmesg snippet
Title is self explanatory. I've looked into similar reports but my dmesg is
different from all of them.
System:
Ryzen 2600
Asus PRIME x470 PRO
16GB of RAM at JEDEC speeds
Reference navi 5700
4K freesync enabled LG display
Arch Linux with lcarlier's mesa-git+llvm-git+xf86-video-amdgpu-git and amd's
staging kernel.
Upon resume I captured this via SSH. System still "works", without screen.
Touching GPU stuff like the debug reset just makes it worse and/or completely
freezes the thing.
Link:
https://pastebin.com/raw/RwnHbvgS
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2684 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-11-10 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 1:11 bugzilla-daemon [this message]
2019-11-19 10:01 ` [Bug 112240] Resume from suspend hangs gfx10 card 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-112240-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.