From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205169] New: AMDGPU driver with Navi card hangs Xorg in fullscreen only.
Date: Sat, 12 Oct 2019 14:24:47 +0000 [thread overview]
Message-ID: <bug-205169-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205169
Bug ID: 205169
Summary: AMDGPU driver with Navi card hangs Xorg in fullscreen
only.
Product: Drivers
Version: 2.5
Kernel Version: 5.4.0-rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: drjoms@gmail.com
Regression: No
I have another problem logged with Navi + AMDGPU drivers. It's triggered
independently and reliable.
https://bugzilla.kernel.org/show_bug.cgi?id=204725
With that said, starting strictly and specifically with kernel version 5.4.0* I
have new problem.
I successfully load into Xorg. I can start OpenGL and Vulkan games in non full
screen. But once I start them - input devices hang, screen freezes. Machine is
responsive over SSH/ethernet. I can raise skinny elephants.
I tried opening a few games in non full screen mode and in full screen mode.
And i reliably hit bug everytime anything with OpenGL goes full screen on
native resolution of the screen.
I noticed, issue is less likely to happen if program goes full screen in non
native resolution.
I will attach details in files for DMESG, lsmod and some other things directly
as message, if they are short enough.
--
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 reply other threads:[~2019-10-12 14:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 14:24 bugzilla-daemon [this message]
2019-10-12 14:35 ` [Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only bugzilla-daemon
2019-10-12 14:37 ` bugzilla-daemon
2019-10-12 14:37 ` bugzilla-daemon
2019-10-12 14:47 ` bugzilla-daemon
2019-10-12 14:48 ` bugzilla-daemon
2019-10-12 16:58 ` bugzilla-daemon
2019-10-13 8:14 ` bugzilla-daemon
2019-10-13 9:43 ` bugzilla-daemon
2019-10-13 9:54 ` bugzilla-daemon
2019-10-14 9:27 ` bugzilla-daemon
2019-10-14 20:04 ` bugzilla-daemon
2019-10-15 20:51 ` bugzilla-daemon
2019-10-30 6:11 ` bugzilla-daemon
2019-11-14 21:59 ` bugzilla-daemon
2019-11-14 22:50 ` bugzilla-daemon
2019-11-14 22:51 ` bugzilla-daemon
2019-11-15 0:06 ` bugzilla-daemon
2019-11-15 1:17 ` bugzilla-daemon
2019-11-15 6:20 ` bugzilla-daemon
2019-11-15 16:03 ` bugzilla-daemon
2019-11-15 19:08 ` bugzilla-daemon
2019-11-15 19:11 ` bugzilla-daemon
2019-11-15 19:52 ` bugzilla-daemon
2019-11-25 1:37 ` bugzilla-daemon
2019-11-25 1:39 ` bugzilla-daemon
2020-02-10 16:12 ` bugzilla-daemon
2021-08-03 15:03 ` 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-205169-2300@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.