[Bug 277638] Crash when running devinfo on RPI CM4
Date: Mon, 11 Mar 2024 20:23:51 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277638 Bug ID: 277638 Summary: Crash when running devinfo on RPI CM4 Product: Base System Version: 15.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: hp@tmm.cx Note: This was also tested on 14.0-RELEASE with the same results. To boot the CM4 it is necessary to set devmatch_enable="NO". This papers over the same crash it seems as gets triggered when running "devinfo" with it enabled. Doing this results in the following backtrace (obtained using kgdb) #0 0xffff00000042b1c8 in doadump (textdump=0, textdump@entry=3234298464) at /usr/src/sys/kern/kern_shutdown.c:403 #1 0xffff0000000efaa4 in db_dump (dummy=<optimized out>, dummy2=<optimized out>, dummy3=<optimized out>, dummy4=<optimized out>) at /usr/src/sys/ddb/db_command.c:590 #2 0xffff0000000ef880 in db_command (last_cmdp=<optimized out>, cmd_table=<optimized out>, dopager=true) at /usr/src/sys/ddb/db_command.c:503 #3 0xffff0000000ef568 in db_command_loop () at /usr/src/sys/ddb/db_command.c:550 #4 0xffff0000000f3050 in db_trap (type=<optimized out>, code=<optimized out>) at /usr/src/sys/ddb/db_main.c:267 #5 0xffff00000047a94c in kdb_trap (type=60, code=0, tf=<optimized out>) at /usr/src/sys/kern/subr_kdb.c:790 #6 <signal handler called> #7 kdb_enter (why=<optimized out>, msg=<optimized out>) at /usr/src/sys/kern/subr_kdb.c:556 #8 0xffff00000042b480 in vpanic (fmt=<optimized out>, ap=...) at /usr/src/sys/kern/kern_shutdown.c:961 #9 0xffff00000042b29c in panic (fmt=0x12 <error: Cannot access memory at address 0x12>) at /usr/src/sys/kern/kern_shutdown.c:889 #10 0xffff00000077e964 in data_abort (td=0xffff0000c3a86c80, frame=0xffff0000c0c783b0, esr=2516582404, far=<optimized out>, lower=0) at /usr/src/sys/arm64/arm64/trap.c:398 #11 <signal handler called> #12 strlcpy (dst=dst@entry=0xffff0000c0c78570 "", src=0xdeadc0dedeadc0de <error: Cannot access memory at address 0xdeadc0dedeadc0de>, dsize=dsize@entry=32) at /usr/src/sys/libkern/strlcpy.c:36 #13 0xffff000000486c4c in sysctl_rman (oidp=<optimized out>, arg1=<optimized out>, arg2=<optimized out>, req=0xffff0000c0c786d0) at /usr/src/sys/kern/subr_rman.c:998 #14 0xffff00000043d3e4 in sysctl_root_handler_locked (oid=oid@entry=0xffff000000a3aa60 <sysctl___hw_bus_rman>, arg1=arg1@entry=0xffff0000c0c787ac, arg2=arg2@entry=3, req=req@entry=0xffff0000c0c786d0, tracker=tracker@entry=0xffff0000c0c78658) at /usr/src/sys/kern/kern_sysctl.c:199 #15 0xffff00000043c754 in sysctl_root (oidp=<optimized out>, arg1=0xffff0000c0c787ac, arg1@entry=0xffff0000c0c787a0, arg2=3, arg2@entry=6, req=req@entry=0xffff0000c0c786d0) at /usr/src/sys/kern/kern_sysctl.c:2407 #16 0xffff00000043cdec in userland_sysctl (td=td@entry=0xffff0000c3a86c80, name=name@entry=0xffff0000c0c787a0, namelen=<optimized out>, old=0x1e0e686d760, oldlenp=<optimized out>, inkernel=<optimized out>, inkernel@entry=-1060665472, new=<optimized out>, newlen=<optimized out>, retval=0xffff0000c0c78798, flags=0) at /usr/src/sys/kern/kern_sysctl.c:2564 #17 0xffff00000043cc68 in sys___sysctl (td=0xffff0000c3a86c80, uap=0xffff0000c3a87080) at /usr/src/sys/kern/kern_sysctl.c:2437 #18 0xffff00000077df4c in syscallenter (td=0xffff0000c3a86c80) at /usr/src/sys/arm64/arm64/../../kern/subr_syscall.c:186 #19 svc_handler (td=0xffff0000c3a86c80, frame=<optimized out>) at /usr/src/sys/arm64/arm64/trap.c:198 #20 do_el0_sync (td=0xffff0000c3a86c80, frame=<optimized out>) at /usr/src/sys/arm64/arm64/trap.c:640 #21 <signal handler called> #22 0x000001e0e9df9944 in ?? () #23 0x000001e0e9d7e888 in ?? () After looking at the code a bit it seems that the "rm" entry is invalid at that point. I don't really know how to continue debugging this. -- You are receiving this mail because: You are the assignee for the bug.