Re: panic shortly after boot when amdgpu.ko is loaded (fpu?)

From: Rebecca Cran <rebecca_at_bsdio.com>
Date: Fri, 27 Nov 2020 11:40:21 -0700
On 11/27/20 11:10 AM, Konstantin Belousov wrote:
> And what is the instruction at 0xffffffff81002dcf ?

I got a much clearer panic by running "sysctl sys" which shows it's more 
likely a problem for the amdgpu folks and not an underlying FreeBSD problem.


#7  0xffffffff810295cd in trap (frame=0xfffffe016e360760)
     at /usr/src/sys/amd64/amd64/trap.c:398
#8  <signal handler called>
#9  0x0000000000000000 in ?? ()
#10 0xffffffff82a14c4e in amdgpu_device_get_pcie_replay_count ()
    from /boot/modules/amdgpu.ko
#11 0xffffffff82a14b80 in sysctl_handle_attr () from /boot/modules/amdgpu.ko
#12 0xffffffff80c06cc1 in sysctl_root_handler_locked 
(oid=0xfffffe02133ff000,
     arg1=0xfffffe016e360980, arg2=-8724518803888, req=0xfffffe016e360980,
     tracker=0xfffff81099af6280) at /usr/src/sys/kern/kern_sysctl.c:184
#13 0xffffffff80c0610c in sysctl_root (oidp=<optimized out>,
     arg1=0xfffff810aa27e650, arg2=-2100190360, req=0xfffffe016e360980)
     at /usr/src/sys/kern/kern_sysctl.c:2211
#14 0xffffffff80c06783 in userland_sysctl (td=0xfffffe00f00b6100,
     name=0xfffffe016e360a40, namelen=4, old=<optimized out>,
     oldlenp=<optimized out>, inkernel=<optimized out>, new=0x0, newlen=0,
     retval=0xfffffe016e360aa8, flags=0)
     at /usr/src/sys/kern/kern_sysctl.c:2368
#15 0xffffffff80c065cf in sys___sysctl (td=0xfffffe00f00b6100,
     uap=0xfffffe00f00b64e8) at /usr/src/sys/kern/kern_sysctl.c:2241
#16 0xffffffff8102a81c in syscallenter (td=0xfffffe00f00b6100)
     at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:189
#17 amd64_syscall (td=0xfffffe00f00b6100, traced=0)
     at /usr/src/sys/amd64/amd64/trap.c:1156
#18 <signal handler called>
#19 0x00000008003819ca in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffffffb618
(kgdb)
Received on Fri Nov 27 2020 - 17:40:27 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:26 UTC