From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206575] [amdgpu] [drm] No video signal on resume from suspend, R9 380
Date: Tue, 18 Feb 2020 17:47:11 +0000 [thread overview]
Message-ID: <bug-206575-2300-4vgfdjMVLq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206575-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206575
Thomas Frank (thfrkbz@e.mail.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thfrkbz@e.mail.de
--- Comment #6 from Thomas Frank (thfrkbz@e.mail.de) ---
I have the same graphics card and the same problem. Do you need additional
dmesg outputs from kernel 5.4.20 and 5.5.4?
I don't know if this helps but I diffed my `amdgpu` filtered dmesg outputs:
```
--- 5.4.20-1-lts_amdgpu_wo_uptime.txt 2020-02-18 18:38:07.393633705 +0100
+++ 5.5.4-arch1-1_amdgpu_wo_uptime.txt 2020-02-18 18:38:32.714488497 +0100
@@ -1,7 +1,4 @@
[drm] amdgpu kernel modesetting enabled.
-amdgpu 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xd0000000 ->
0xdfffffff
-amdgpu 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xe0000000 ->
0xe01fffff
-amdgpu 0000:01:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xefe00000 ->
0xefe3ffff
fb0: switching to amdgpudrmfb from VESA VGA
amdgpu 0000:01:00.0: vgaarb: deactivate vga console
amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF
(4096M used)
@@ -9,7 +6,9 @@
[drm] amdgpu: 4096M of VRAM memory ready
[drm] amdgpu: 4096M of GTT memory ready.
amdgpu: [powerplay] hwmgr_sw_init smu backed is tonga_smu
+[drm:dm_helpers_parse_edid_caps [amdgpu]] *ERROR* Couldn't read SADs: -2
fbcon: amdgpudrmfb (fb0) is primary device
amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
-[drm] Initialized amdgpu 3.35.0 20150101 for 0000:01:00.0 on minor 0
+[drm] Initialized amdgpu 3.36.0 20150101 for 0000:01:00.0 on minor 0
snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops
amdgpu_dm_audio_component_bind_ops [amdgpu])
+[drm:dm_helpers_parse_edid_caps [amdgpu]] *ERROR* Couldn't read SADs: -2
```
The last line from the diff
`[drm:dm_helpers_parse_edid_caps [amdgpu]] *ERROR* Couldn't read SADs: -2`
happens after resuming (with blank screen).
--
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 prev parent reply other threads:[~2020-02-18 17:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:28 [Bug 206575] New: [amdgpu] [drm] No video signal on resume from suspend, R9 380 bugzilla-daemon
2020-02-17 16:29 ` [Bug 206575] " bugzilla-daemon
2020-02-17 16:29 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:33 ` bugzilla-daemon
2020-02-17 16:38 ` bugzilla-daemon
2020-02-18 17:47 ` bugzilla-daemon [this message]
2020-02-18 21:33 ` bugzilla-daemon
2020-02-18 21:44 ` bugzilla-daemon
2020-02-18 22:06 ` bugzilla-daemon
2020-02-19 19:51 ` bugzilla-daemon
2020-02-21 0:42 ` bugzilla-daemon
2020-02-24 2:12 ` bugzilla-daemon
2020-03-16 9:39 ` bugzilla-daemon
2020-03-20 19:54 ` bugzilla-daemon
2020-03-20 20:15 ` bugzilla-daemon
2020-03-20 22:03 ` bugzilla-daemon
2020-03-23 5:06 ` bugzilla-daemon
2020-03-24 20:11 ` bugzilla-daemon
2020-04-10 8:35 ` bugzilla-daemon
2020-04-11 13:56 ` bugzilla-daemon
2020-04-11 13:59 ` bugzilla-daemon
2020-04-14 9:09 ` bugzilla-daemon
2020-04-14 13:28 ` bugzilla-daemon
2020-04-14 13:31 ` bugzilla-daemon
2020-04-14 14:10 ` bugzilla-daemon
2020-04-15 11:43 ` bugzilla-daemon
2020-04-15 11:44 ` bugzilla-daemon
2020-04-15 11:45 ` 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-206575-2300-4vgfdjMVLq@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.