From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108294] Turning off monitor via DisplayPort causes Kernel warning + stack trace
Date: Tue, 09 Oct 2018 07:44:58 +0000 [thread overview]
Message-ID: <bug-108294-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2754 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108294
Bug ID: 108294
Summary: Turning off monitor via DisplayPort causes Kernel
warning + stack trace
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: jamespharvey20@gmail.com
Created attachment 141955
--> https://bugs.freedesktop.org/attachment.cgi?id=141955&action=edit
kernel warning + stack trace - from when HDMI monitor is turned off and back on
Up to date Arch Linux, including: linux 4.18.12.arch1-1, xf86-video-amdgpu
18.1.0-1, mesa 18.2.2-1, opencl-mesa 18.2.2-1, xorg-server 1.20.1-1, and
plasma-desktop 5.13.5-1.
(Recently installed system that STARTED with: linux 4.18.9.arch1-1, mesa
18.2.1-1, and opencl-mesa 18.2.1-1.) It was also doing this then.
$ lspci -k | grep VGA
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Ellesmere [Radeon RX 470/480/570/570X/580/580X] (rev e7)
Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX
470/480/570/570X/580/580X]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
It's the: XFX AMD Radeon RX 580 GTS Black Edition 8GB GDDR5 PCI Express 3.0
I have (5) Acer K272HUL bmiidp monitors hooked up via DisplayPort. Left 2 are
chained, and right 2 are chained.
ASRock EP2C602 Motherboard w/ P1.90 BIOS. (2) Intel Xeon E5-2690 (v1).
Anytime a monitor turns off, it causes a couple of kernel warnings and stack
traces. Usually 2-3 warnings each time.
When the monitor turns back on, it just logs what are I think are (3) expected
"[drm]" lines about the "new" connection.
See attached file for a sample of the kernel warnings/stack traces. The first
part is when a monitor turned off, and the last part is when it turned back on.
By turned off/on, I mean regardless of if I press its power button on the
monitor, pull the plug and plug it back in, or if a graphics issue somewhere in
a driver or graphics API turns off a monitor until I cycle it.
The only time I'm having this now is occasionally a few programs that use
OpenGL graphics. (Monitors turning off/back on was happening a lot with the
Acer-provided DisplayPort cables, but replacing them with certified Accell
UltraAV DisplayPort cables fixed that.)
When I turn it back on, KDE/Plasma properly re-adds it, gives it the right
resolution, rotation, and alignment next to the other monitors.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4322 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-10-09 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:44 bugzilla-daemon [this message]
2018-10-09 7:52 ` [Bug 108294] Turning off monitor via DisplayPort causes Kernel warning + stack trace bugzilla-daemon
2019-11-19 8:57 ` 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-108294-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.