From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216277] New: X11 doesn't wait for amdgpu driver to be up
Date: Sun, 24 Jul 2022 14:55:50 +0000 [thread overview]
Message-ID: <bug-216277-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216277
Bug ID: 216277
Summary: X11 doesn't wait for amdgpu driver to be up
Product: Drivers
Version: 2.5
Kernel Version: 5.18.11+
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: dark_sylinc@yahoo.com.ar
Regression: No
# Context
I'm using Xubuntu 20.04
I compiled Kernel 5.18.11+ myself (shows bug)
I compiled Kernel 5.13.7+ myself (does not show bug)
My GPU is AMD Radeon 6800 XT 16GB, I don't have an iGPU (CPU is Ryzen 5900X)
Mesa is:
OpenGL renderer string: AMD Radeon RX 6800 XT (sienna_cichlid, LLVM 14.0.1, DRM
3.46, 5.18.11+)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.5 - kisak-mesa
PPA
OpenGL core profile shading language version string: 4.60
# Steps to reproduce
1. Turn on the PC
2. On *some* occasions X11 will crash, taking down the keyboard; leaving the
computer in a seemingly frozen state while displaying tty with the last info
messages
3. As a workaround, I can login via ssh and type `sudo service lightdm restart`
and the X11 server will start and everything starts working perfectly fine
# Diagnostic
It seems X11 doesn't wait for amdgpu to be up. This can be seen by checking
/var/log/Xorg.0.log (attached):
[ 7.718] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 7.718] (II) FBDEV: driver for framebuffer: fbdev
[ 7.718] (II) VESA: driver for VESA chipsets: vesa
[ 7.718] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 7.718] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[ 7.719] (EE) open /dev/dri/card0: No such file or directory
[ 7.719] (WW) Falling back to old probe method for modesetting
[ 7.719] (EE) open /dev/dri/card0: No such file or directory
Visually speaking, I *think* that X11 tries to init while tty is still in VESA
mode before/during switching to 1920x1080
AFAIK, systemd is responsible for waiting the GPU drivers are up. Does anybody
know where I should look? Does systemd need an update? Could this be a libDRM
issue? I currently have installed 2.4.110 in /usr/lib and libdrm 2.4.111
compiled from source in /usr/local/lib
I could try bisecting but unfortunately the reproducibility isn't "always"
which makes it hard to debug.
All of this has been working fine with Kernel 5.13.7+
Cheers
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-07-24 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 14:55 bugzilla-daemon [this message]
2022-07-24 14:56 ` [Bug 216277] X11 doesn't wait for amdgpu driver to be up bugzilla-daemon
2022-07-24 14:56 ` bugzilla-daemon
2022-07-25 15:46 ` bugzilla-daemon
2022-07-25 16:07 ` bugzilla-daemon
2022-07-25 16:27 ` bugzilla-daemon
2022-07-26 15:35 ` bugzilla-daemon
2022-08-10 0:17 ` 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-216277-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.