20:31 <jaeger> hrmm... having a weird issue with vulkan on this system... ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers!

20:31 <jaeger> using an AMD GPU (RX580) that has worked in the past with the amdgpu kernel DRI/DRM driver

20:31 <jaeger> I've rebuilt all the vulkan packages with no luck

20:35 <jaeger> Wonder if maybe it's wayland/xwayland not working, guess I should try it with a normal X session

20:39 <jaeger> ok, same in plain X

20:39 <ukky> jaeger: Can you strace the loading process? Any chance that your system has extra libc.so or libstdc++.so on the lib path?

20:40 <jaeger> I can't imagine where an extra libc or libstdc++ would come from but yeah, going to try strace next

20:41 <beerman> which kernel are you using? I am hitting a weird bug with with everything 6.1.z upwards

20:41 <beerman> not this though, i barely get a working session and if i get i am easy to trigger a fault in amdgpu and it just crashes

20:41 <beerman> with my rx580..

20:42 <jaeger> 6.1.61

20:43 <jaeger> sway by itself seems to behave just fine

20:43 <jaeger> Though I did have one odd firefox crash when opening a file save dialog

20:44 <ukky> jaeger: Just a few days ago I couldn't load /usr/lib64/dri/nouveau_dri.so because an SDK from 2020 places ancient libstdc++.so on the lib path when SDK loads.

20:44 <jaeger> What SDK was that?

20:44 <ukky> Xilinx Vitis 2020.2

20:44 <jaeger> definitely not using that here, never heard of it

20:45 <ukky> It's being used for FPGA chips

20:46 <jaeger> Yeah, I looked it up

20:46 <jaeger> Ah ha! Found the problem, radeon_icd.x86_64.json was corrupted somehow, had garbage in it

20:46 <jaeger> rebuilt mesa ports to recreate it, works now in X at least

20:47 <jaeger> and seems to work in wayland too, good

20:47 <beerman> ah, weird

20:48 <ukky> Are you loading it as root?

20:49 <jaeger> nope

20:49 <jaeger> and of course my user is in the video group, etc.

20:49 <jaeger> It was just the file from mesa being messed up

20:49 <ukky> ok

20:50 <jaeger> Always something new, heh. Hadn't seen that happen before.

20:52 <beerman> yeah :)

21:05 <beerman> [ 53.142282] BUG: kernel NULL pointer dereference, address: 0000000000000008

21:06 <beerman> just checked, i get this beauty after turning the monitors off and then turning them back on. same is triggered when the screen gets locked and it sends the monitors to sleep

21:06 <beerman> 6.0.whatever works flawlessly. 6.1 upwards produces this

21:14 <ukky> beerman: Any call stack dumped at panic? The following seems relevant: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1981658/comments/36

21:17 <beerman> ukky thanks for checking in. while i researched a bit, it seemed like its not the first time that amdgpu suffered such a bad bug for way too long. But I don't have a hub attached, and I haven't tried unplugging anything to see if this unfucks it. Even if it would, I dunno what that would mean for me

21:18 <beerman> actually one thing. and while we are talking about, i'll try throwing that out

21:19 <beerman> well that and a bios update I guess..

21:22 <ukky> Power management related bugs are nasty. Sometimes the reason for the issue is the bug in ACPI tables in the System BIOS.

21:32 <beerman> yeah, the one thing (supposedly bad pcie card) doesn't seem to do any difference. i'll try the bios update next

21:47 <beerman> It's not the BIOS either

21:50 <ukky> Have anybody seen, or reported similar issue with non-AMD graphics?

22:09 <beerman> I don't think that I can remember anything for other vendors