From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106317] System lock up after monitors wake from DPMS on Ryzen 3 2200g
Date: Mon, 30 Apr 2018 04:51:49 +0000 [thread overview]
Message-ID: <bug-106317-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2832 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106317
Bug ID: 106317
Summary: System lock up after monitors wake from DPMS on Ryzen
3 2200g
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: laszlo.kertesz@gmail.com
I have a Ryzen 3 2200g CPU on a Gigabyte AB350M-HD3 mobo. I have 2 monitors
connected (same model), one via HDMI, the other via DVI.
OS: Debian Testing, kernel compiled from mainline git (rc2+ now, after the rc3
DRM fixes patches merge). But this issue is present even with the kernel from
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.18-wip
The issue i encounter is the when the monitors enter dpms and tries to wake,
the system freezes.
This is not happening always, but it can be reproduced reliably with running
"DISPLAY=:0 xset dpms force off"
Repeatedly. It will eventually lock up (minimum tries was 1, max 9).
One of the monitors (HDMI) will have the signal still cut, the other (DVI) will
have a blank signal (this behavior seems consistent).
The system freezes totally (no ssh access, ping, magic keys etc). Also no
usable logs. This is compounded by the issue of having to reboot repeatedly
after this issue since the system will freeze at reboot when the KMS mode is
enabled.
Maybe unrelated but i have this line in dmesg after each boot:
[ 5.312547] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector
ObjectID from Adapter Service for connector index:2! type 0 expected 3
xrandr output:
HDMI-A-0 connected primary 1440x900+1440+0 (normal left inverted right x axis y
axis) 408mm x 255mm
1440x900 59.89*+ 74.98
1280x1024 75.02 60.02
1280x800 59.89
1152x864 75.00
1280x720 59.89
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 59.94
720x400 70.08
DVI-D-0 connected 1440x900+0+0 (normal left inverted right x axis y axis) 408mm
x 255mm
1440x900 59.89*+ 74.98
1280x1024 75.02 60.02
1280x800 59.89
1152x864 75.00
1280x720 59.89
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 59.94
720x400 70.08
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4211 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-04-30 4:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 4:51 bugzilla-daemon [this message]
2018-04-30 9:00 ` [Bug 106317] System lock up after monitors wake from DPMS on Ryzen 3 2200g bugzilla-daemon
2018-04-30 14:14 ` bugzilla-daemon
2018-04-30 14:24 ` bugzilla-daemon
2018-04-30 19:50 ` bugzilla-daemon
2018-04-30 19:52 ` bugzilla-daemon
2018-06-01 18:52 ` bugzilla-daemon
2018-06-01 19:02 ` bugzilla-daemon
2019-11-19 8:37 ` 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-106317-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.