You are not logged in.
- Topics: Active | Unanswered
#1 2020-01-08 22:34:22
- RedSea
- Member
- Registered: 2020-01-08
- Posts: 4
[Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Hello guys,
I am trying to install amdgpu-pro drivers using aurman from the AUR, the specific package is this one https://aur.archlinux.org/packages/amdgpu-pro-libgl, but as the title of my thread suggests once i reboot to use the new drivers GDM takes ages to come up, this doesn't happen with the free drivers.
I am pasting the logs from a journalctl -xb on pastebin (https://pastebin.com/YuduHVnL).
Here is the journalctl -p 3 -xb which identifies a segfault with wayland, which is probably causing the issue I have, but i don't want to jump to conclusions:
cat journalctlOut
-- Logs begin at Wed 2019-12-18 19:41:28 WET, end at Wed 2020-01-08 22:09:56 WET. --
Jan 08 21:59:42 SamSepi0l-Arch systemd-udevd[548]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
Jan 08 22:00:09 SamSepi0l-Arch systemd[828]: Failed to start GNOME Shell on Wayland.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 111 and the job result is failed.
Jan 08 22:00:09 SamSepi0l-Arch systemd-coredump[906]: Process 871 (Xwayland) of user 120 dumped core.
Stack trace of thread 871:
#0 0x00007f6d8208ef25 raise (libc.so.6 + 0x3bf25)
#1 0x00007f6d82078897 abort (libc.so.6 + 0x25897)
#2 0x00005563a62560ca n/a (Xwayland + 0x640ca)
#3 0x00005563a62595cc n/a (Xwayland + 0x675cc)
#4 0x00005563a625d9fb n/a (Xwayland + 0x6b9fb)
#5 0x00007f6d8208efb0 __restore_rt (libc.so.6 + 0x3bfb0)
#6 0x00007f6d7e513ad3 n/a (amdgpu_dri.so + 0xffdad3)
#7 0x00007f6d7e9d8aec n/a (amdgpu_dri.so + 0x14c2aec)
#8 0x00007f6d7e69a245 n/a (amdgpu_dri.so + 0x1184245)
#9 0x00007f6d7e871e63 eglCreateImageKHR (amdgpu_dri.so + 0x135be63)
#10 0x00005563a636d75d n/a (Xwayland + 0x17b75d)
#11 0x00005563a63743c7 n/a (Xwayland + 0x1823c7)
#12 0x00005563a631b01e n/a (Xwayland + 0x12901e)
#13 0x00005563a631f056 n/a (Xwayland + 0x12d056)
#14 0x00005563a6221efd n/a (Xwayland + 0x2fefd)
#15 0x00007f6d8207a153 __libc_start_main (libc.so.6 + 0x27153)
#16 0x00005563a622302e n/a (Xwayland + 0x3102e)
Stack trace of thread 887:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 889:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 880:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 885:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 882:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 884:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 890:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 883:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 881:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 888:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 879:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab4a514 n/a (swrast_dri.so + 0x19f514)
#2 0x00007f6d7ab4a368 n/a (swrast_dri.so + 0x19f368)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
Stack trace of thread 886:
#0 0x00007f6d81518c45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfc45)
#1 0x00007f6d7ab48024 n/a (swrast_dri.so + 0x19d024)
#2 0x00007f6d7ab47fa8 n/a (swrast_dri.so + 0x19cfa8)
#3 0x00007f6d815124cf start_thread (libpthread.so.0 + 0x94cf)
#4 0x00007f6d821522d3 __clone (libc.so.6 + 0xff2d3)
-- Subject: Process 871 (Xwayland) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 871 (Xwayland) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.Failed to start gnome shell on wayland is what i spot as the problem...
I don't really know why this is happening, or what I can do to fix this.
From the searches i have been through, hangs before GDM has to do with entropy, this is not the case here as can be seen from the logs, but to be on the safe side i tried to install havaged to check if something changed, it still hangs.
Hopefully you guys can shed some light on the issue.
Thanks in Advance
System Specs:
CPU - intel core i5 9600k
Mobo - MSI Tomahawk Z390
RAM - Kingston 32gb of ram 2400Mhz
GPU - AMD Radeon RX 580 8gb vram
Kernel - Linux SamSepi0l-Arch 5.4.8-arch1-1 #1 SMP PREEMPT Sat, 04 Jan 2020 23:46:18 +0000 x86_64 GNU/Linux
Last edited by RedSea (2020-01-12 16:40:51)
Offline
#2 2020-01-09 14:49:44
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,911
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Note: when attaching journalctl output to bug reports, please do not use -x.
Not easy to find with all those explanations, but this looks weird.
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: Failed to query device string: The last function succeeded without error.
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: g_str_has_prefix: assertion 'str != NULL' failed
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: g_str_has_prefix: assertion 'str != NULL' failed
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: g_str_has_prefix: assertion 'str != NULL' failed
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: Failed to get string: No error has been recorded.
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: g_strjoinv: assertion 'str_array != NULL' failed
Jan 08 22:00:05 SamSepi0l-Arch gnome-shell[854]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Missing OpenGL ES extensions: (null)
Jan 08 22:00:06 SamSepi0l-Arch gnome-shell[871]: glamor: No eglstream capable devices foundAs far as I know eglstream is only used on nvidia videocards, something in your configuration seems very wrong .
post lspci -k and journalctl -b .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#3 2020-01-09 17:45:09
- RedSea
- Member
- Registered: 2020-01-08
- Posts: 4
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Hey Lone_Wolf, first of all thank you for taking the time to help me out.
Secondly
man journalctl wrote:
Note: when attaching journalctl output to bug reports, please do not use -x.
Damn it! I am sorry, here is a journalctl -b (https://pastebin.com/uhjGnqBq)
here is the lspci -k
lspci -k
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 0a)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] 8th Gen Core Processor Host Bridge/DRAM Registers
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 0a)
Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH Thermal Controller
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH USB 3.1 xHCI Host Controller
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
DeviceName: Onboard - Other
Subsystem: Intel Corporation Cannon Lake PCH Shared SRAM
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH HECI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
DeviceName: Onboard - SATA
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH SATA AHCI Controller
Kernel driver in use: ahci
Kernel modules: ahci
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #4 (rev f0)
Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Z390 Chipset LPC/eSPI Controller
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
DeviceName: Onboard - Sound
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH cAVS
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH SMBus Controller
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
DeviceName: Onboard - Other
Subsystem: Micro-Star International Co., Ltd. [MSI] Cannon Lake PCH SPI Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
DeviceName: Onboard - Ethernet
Subsystem: Micro-Star International Co., Ltd. [MSI] Ethernet Connection (7) I219-V
Kernel driver in use: e1000e
Kernel modules: e1000e
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7)
Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC
Kernel driver in use: amdgpu
Kernel modules: amdgpu
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
Kernel driver in use: nvme
04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
Subsystem: Micro-Star International Co., Ltd. [MSI] I211 Gigabit Network Connection
Kernel driver in use: igb
Kernel modules: igbThanks a lot Lone_Wolf
Best regards,
Offline
#4 2020-01-11 15:34:50
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,911
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
It looks like gdm tries to start a wayland sesssion using amdgpu-pro but fails, then falls back to an Xorg session.
While wayland normally uses GBM this doesn't work with nvidia proprietary driver.
Nvidia does support another method, eglstreams . Gnome and KDE have code to run wayland over eglstreams.
I have no idea if the amdgpu-pro driver supports GBM and estimate the chance it supports eglstreams smaller then the chance to win a lottery you don't particpate in.
Xorg on your system is not configured to use the amdgpu-pro driver.
Do you want to use wayland ?
The opensource amdgpu driver is equal or better to amdgpu-pro for most usecases, is there a specific reason you want the amdgpu-pro driver ?
Last edited by Lone_Wolf (2020-01-11 15:35:17)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#5 2020-01-11 17:36:17
- RedSea
- Member
- Registered: 2020-01-08
- Posts: 4
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Hey Lone_Wolf,
That's what i gathered from the log as well, i just don't know why it fails, this is a fresh system, installed it, added users, added gnome and gdm and tried to install the proprietary drivers, didn't mess around much.
No I don't particularly need to run on wayland, xorg is absolutely fine.
Regarding the driver, well i have been reading that as well, I am not entirely sure, I am going to use it for hash cracking and gaming, should i go for the open-source version? is it better?
What do you recommend doing in order to fix this?
Thanks in advanced,
PS. Forgot to mention, this is using a dual monitor setup, I don't know if that makes any difference, both hooked at Amd rx 580
Last edited by RedSea (2020-01-11 17:41:09)
Offline
#6 2020-01-11 22:00:54
- apaz
- Member
- Registered: 2018-07-23
- Posts: 116
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
For gaming and normal desktop use, amdgpu open are much better. Amdgpu-pro are only needed to have OpenCL (and OpenGL) with programs like Blender, Davinci Resolve, Fusion, etc.
Offline
#7 2020-01-12 11:03:43
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,911
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Setup gdm to start Xorg, https://wiki.archlinux.org/index.php/GD … rg_backend
The opensource amdgpu driver is weak on OpenCL support (max opencl 1.1) , but otherwise very capable.
I suggest using mesa + xf86-video-amdgpu with aur opencl-amd for OpenCL support.
In this setup mesa provides OpenGL, while OpenCL is provided by opencl-amd .
Some programs expect both to be provided by the same driver and may fail if that's not the case.
Davinci Resolve had big problems with this setup a few months ago, no idea if it works better now.
https://wiki.archlinux.org/index.php/GPGPU has an overview
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#8 2020-01-12 16:39:55
- RedSea
- Member
- Registered: 2020-01-08
- Posts: 4
Re: [Solved] AMDGPU-PRO driver hangs for a minute before reaching GDM
Hey guys thanks for the input,
So yeah Lone_Wolf, enabling the start with xorg instead of wayland fixes the issue.
But now I am curious about what you suggested with the open source driver, and I am going to have a look through the wiki.
Still the issue is solved, so I am going to mark it as solved.
Thanks a lot guys,
Best regards
Offline