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@xxxxxxxxxxxxxxxxxxxx Reporter: dark_sylinc@xxxxxxxxxxxx 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.
