I found a kernel panic when "r600_cp: Failed to load firmware "radeon/RS780_pfp.bin" in newly upgraded openbsd 7.7 in both kernels bsd.sp and bsd.mp
When I used old 7.6 kernel (o)bsd it worked around a fail to load drm firmware: ... r600_cp: Failed to load firmware "radeon/RS780_pfp.bin" [drm] *ERROR* Failed to load firmware! drm:pid0:radeondrm_attachhook *ERROR* Fatal error during GPU init drm0 detached radeondrm0 detached ... First question is where is missed firmware and a second question is how new kernels works around the problem. In attached dmesg.boot there is a few boots of new 7.7, bsd.rd and old 7.6 kernel: OpenBSD 7.7 (GENERIC.MP) #625: Sun Apr 13 08:30:20 MDT 2025 OpenBSD 7.7 (GENERIC.MP) #625: Sun Apr 13 08:30:20 MDT 2025 OpenBSD 7.7 (RAMDISK_CD) #613: Sun Apr 13 08:35:08 MDT 2025 OpenBSD 7.7 (GENERIC.MP) #625: Sun Apr 13 08:30:20 MDT 2025 OpenBSD 7.7 (RAMDISK_CD) #613: Sun Apr 13 08:35:08 MDT 2025 OpenBSD 7.6 (GENERIC.MP) #338: Mon Sep 30 08:55:35 MDT 2024 OpenBSD 7.7 (GENERIC) #619: Sun Apr 13 08:19:34 MDT 2025 OpenBSD 7.7 (RAMDISK_CD) #613: Sun Apr 13 08:35:08 MDT 2025 OpenBSD 7.6 (GENERIC.MP) #338: Mon Sep 30 08:55:35 MDT 2024 Please consider review of above problem. Thank You best regards Zbigniew Kossowski ---------- Forwarded message --------- Od: Nick Owens <[email protected]> Date: niedz., 25 maj 2025 o 21:58 Subject: Re: Kernel panic To: Zbigniew Kossowski <[email protected]> Cc: misc <[email protected]> On Sun, May 25, 2025, 06:40 Zbigniew Kossowski <[email protected]> wrote: > I have provided manual upgrade in a remote machine as in > https://www.openbsd.org/faq/upgrade77.html > > I did it for several times before. After the first reboot I have got a > kernel panic on bsd(.mp) and bsd(.sp). Older kernel (o)bsd 7.6 works fine, > but it is mix up now. I have got a picture of the screen so it is not a > full dmesg: > ... > radeondrm0: RS880 > r600_cp: Failed to load firmware "radeon/RS780_pfp.bin" > panic: pool_destroy: pool busy: still out: 2 > ... > ddb> > > I did this upgrade a few times to be sure that I didn't an error. > Same result. > > Please suggest what to do in that situation. > start with reading https://www.openbsd.org/report.html - at the very least providing your full dmesg and show panic, trace and ps from ddb would probably be useful to someone investigating this. > > Regards > Zbigniew Kossowski > >
dmesg.boot
Description: Binary data
