panic loading amdgpu

[rkitover]

I get this in /var/log/messages:

Dec 24 01:14:03 epycfbsd kernel: drmn1: failed to link firmware kernel module with mapped name: amdgpu_navi10_gpu_info_bin
Dec 24 01:14:03 epycfbsd kernel: amdgpu/navi10_gpu_info.bin: could not load firmware image, error 2
Dec 24 01:14:03 epycfbsd syslogd: last message repeated 1 times
Dec 24 01:14:03 epycfbsd kernel: drmn1: failed to load firmware with name: amdgpu/navi10_gpu_info.bin
Dec 24 01:14:03 epycfbsd kernel: drmn1: Failed to load gpu_info firmware "amdgpu/navi10_gpu_info.bin"
Dec 24 01:14:03 epycfbsd kernel: drmn1: Fatal error during GPU init
Dec 24 01:14:03 epycfbsd kernel: [drm] amdgpu: finishing device.
Dec 24 01:14:03 epycfbsd kernel: Warning: can't remove non-dynamic nodes (dri)!

I am using latest git current with latest git drm-devel-kmod and gpu-firmware-kmod from ports.

My card is a 5700xt.

Any help much appreciated.

[valpackett]

Well do you have the firmware installed? It's packaged as gpu-firmware-kmod.

[rkitover]

Yes I have the latest drm-devel-kmod and gpu-firmware-kmod installed from the ports git.

[valpackett]

Weird. Can you manually kldload amdgpu_navi10_gpu_info_bin?

[rkitover]

I will try right now.

[rkitover]

So that loads fine, but it seems that amdgpu dies with a backtrace which I need to get with hw.syscons.disable=1 which might be tricky.

[valpackett]

Drop the syscons.disable and just make sure the loader is not in the highest/"native" resolution (check with the gop command in the loader prompt) (set efi_max_resolution="1080p" or efi_max_resolution="720p" or whatever would make it smaller in loader.conf`), there should be no framebuffer problems in that case

[rkitover]

Nice, thank you, I will try that.

[rkitover]

I set the resolution to 1440p and the framebuffer started at 1600x1200.

I ran:

kldload amdgpu_navi10_gpu_info_bin
kldload amdgpu

I got this backtrace:

Here is my system information:

Motherboard: Supermicro H11DSi
CPUs: 2x 32 core first gen AMD epyc
RAM: 128gb ECC
GPUs: 2x 5700xt
FreeBSD: latest current git
Packages: latest from pkg
Ports: latest git versions of drm-devel-kmod and gpu-firmware-kmod

If you would like to debug this, I'll be happy to do whatever is needed.

[valpackett]

2x 5700xt

huh. well the panic is that the driver is trying to create /dev/dri/renderD128 twice (error code 17 is EEXIST). Looks like the first GPU failed to attach for some actual, more serious reason (drmn0 attach returned 2 at the very top line), and we don't clean everything up in that case, so the second GPU fails with that.

Can you scroll up (with Scroll Lock) in the console to see what's up with the first GPU?

[rkitover]

This time I got somewhat different behavior, I ran:

kldload amdgpu

and it initialized the first card and loaded the firmware, I could see the firmware modules in kldstat. However, it failed to initialize the second card.

Here is the first card being successfully initialized:

Here is the second card failing to initialize:

I then tried running xorg with amdgpu to see if it would start on the first card, but I got a panic:

[valpackett]

hm, same trace as freebsd/drm-kmod#36 with the vm_page_busy_acquire

Try building the newer driver from freebsd/drm-kmod#40 (https://github.com/myfreeweb/drm-kmod/tree/5.5-wip-amd-pr)

[rkitover]

I built and installed that branch, and now I get this backtrace on kldload amdgpu, this is the first page:

and this is the second page:

[valpackett]

welcome to the navi FPU kernel context issues suffering club :D (freebsd/drm-kmod#42 etc)

Please try again (git pull to get the latest commit freebsd/drm-kmod@c4cc838)

[rkitover]

Thank you, that seems to have gotten further, but still panics:

Looks to be dying in the same function.