From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 109539] System freezing
Date: Sun, 03 Feb 2019 20:36:56 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1425101104=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 331C66E250
for ; Sun, 3 Feb 2019 20:36:57 +0000 (UTC)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1425101104==
Content-Type: multipart/alternative; boundary="15492262170.4EA7.5703"
Content-Transfer-Encoding: 7bit
--15492262170.4EA7.5703
Date: Sun, 3 Feb 2019 20:36:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D109539
Bug ID: 109539
Summary: System freezing
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: jon780@gmail.com
Created attachment 143282
--> https://bugs.freedesktop.org/attachment.cgi?id=3D143282&action=3Dedit
journalctl
Fedora 29
kernel 4.20.5 (compiled to try something newer than in the fedora repos)
Ryzen 1700X
MSI B350 Tomawhawk (Arctic)
Three Dell U2415 monitors (one dvi, one hdmi, one displayport).
Freezing when waking from sleep, usually withing just a few seconds. Examp=
le
journactl attached. When it freezes, the mouse can still move, but no other
input. Cannot click, cannot switch to virtual terminals, cannot send REISU=
B,
cannot toggle off numlock (light frozen). Only thing that fixes it is a re=
boot
of the computer.
Setting amdgpu.dc=3D0 appears to resolve the issue! Went from freezing when
waking from sleep several times a day to >24 hours of uptime so far.
Also, when DC is enabled, displayport monitor will not wake from sleep. The
only want I can get it to wake is xrandr --off and then --auto on the
DisplayPort. I also want to mention that the displayport name changes every
time it sleeps and wakes (DisplayPort-1, DisplayPort-2, DisplayPort-3) even
though nothing is really being moved to a different port.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15492262170.4EA7.5703
Date: Sun, 3 Feb 2019 20:36:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
| Bug ID |
109539
|
| Summary |
System freezing
|
| 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 |
jon780@gmail.com
|
Created attachment 143282 [det=
ails]
journalctl
Fedora 29
kernel 4.20.5 (compiled to try something newer than in the fedora repos)
Ryzen 1700X
MSI B350 Tomawhawk (Arctic)
Three Dell U2415 monitors (one dvi, one hdmi, one displayport).
Freezing when waking from sleep, usually withing just a few seconds. Examp=
le
journactl attached. When it freezes, the mouse can still move, but no other
input. Cannot click, cannot switch to virtual terminals, cannot send REISU=
B,
cannot toggle off numlock (light frozen). Only thing that fixes it is a re=
boot
of the computer.
Setting amdgpu.dc=3D0 appears to resolve the issue! Went from freezing when
waking from sleep several times a day to >24 hours of uptime so far.
Also, when DC is enabled, displayport monitor will not wake from sleep. The
only want I can get it to wake is xrandr --off and then --auto on the
DisplayPort. I also want to mention that the displayport name changes every
time it sleeps and wakes (DisplayPort-1, DisplayPort-2, DisplayPort-3) even
though nothing is really being moved to a different port.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15492262170.4EA7.5703--
--===============1425101104==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1425101104==--