[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028

--- Comment #125 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
Well, I was going to try testing in an environment were I've
got a serial console: an aarch64 main [so: 14] context. But
it turns out that there is at least one missing function
declaration foor the type of context at this point:

/wrkdirs/usr/ports/graphics/drm-515-kmod/work/drm-kmod-drm_v5.15.25/drivers/gpu/drm/drm_cache.c:362:10:
error: call to undeclared function 'in_interrupt'; ISO C99 and later do not
support implicit function declarations
[-Werror,-Wimplicit-function-declaration]
        WARN_ON(in_interrupt());
                ^
1 error generated.
*** [drm_cache.o] Error code 1

as is visible in the official build log:

http://ampere2.nyi.freebsd.org/data/main-arm64-default/p64e3eb722c17_s7fc82fd1f8/logs/errors/drm-515-kmod-5.15.25.log

Turns out the drm-510-kmod variant allowed for releng/13.1
and later is missing possible macro definitions for aarch64:

/wrkdirs/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_2/drivers/gpu/drm/amd/display/dc/core/dc.c:741:3:
error: call to undeclared function 'DC_FP_START'; ISO C99 and later do not
support implicit function declarations
[-Werror,-Wimplicit-function-declaration]
                DC_FP_START();
                ^
/wrkdirs/usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_2/drivers/gpu/drm/amd/display/dc/core/dc.c:743:3:
error: call to undeclared function 'DC_FP_END'; ISO C99 and later do not
support implicit function declarations
[-Werror,-Wimplicit-function-declaration]
                DC_FP_END();
                ^
2 errors generated.
*** [dc.o] Error code 1

as is visible in:

http://ampere2.nyi.freebsd.org/data/main-arm64-default/p64e3eb722c17_s7fc82fd1f8/logs/errors/drm-510-kmod-5.10.163_2.log

(It is not just my builds that have such issues:
official builds have the problems as well.)

I was hoping I'd be able to do some testing in the
alternative type of context (likely never starting
X11). That looks to not be in the cards at this
time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.