Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Dec 2024 16:17:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 283159] crash dump backtraces broken on arm64
Message-ID:  <bug-283159-227-tA3gnSYyYP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-283159-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-283159-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283159

Mark Johnston <markj@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
                 CC|                            |jhb@FreeBSD.org,
                   |                            |markj@FreeBSD.org

--- Comment #1 from Mark Johnston <markj@FreeBSD.org> ---
I can't reproduce this on my devkit:

Reading symbols from /boot/kernel/zfs.ko...
Reading symbols from /usr/lib/debug//boot/kernel/zfs.ko.debug...
Reading symbols from /boot/kernel/mac_ntpd.ko...
Reading symbols from /usr/lib/debug//boot/kernel/mac_ntpd.ko.debug...
0xffff0000004b5aac in doadump (textdump=3Dtextdump@entry=3D1) at
/root/freebsd/sys/kern/kern_shutdown.c:404
warning: 404    /root/freebsd/sys/kern/kern_shutdown.c: No such file or
directory
(kgdb) bt
#0  0xffff0000004b5aac in doadump (textdump=3Dtextdump@entry=3D1) at
/root/freebsd/sys/kern/kern_shutdown.c:404
#1  0xffff0000004b586c in kern_reboot (howto=3D260) at
/root/freebsd/sys/kern/kern_shutdown.c:524
#2  0xffff0000004b5dec in vpanic (fmt=3D<optimized out>, ap=3D...) at
/root/freebsd/sys/kern/kern_shutdown.c:979
#3  0xffff0000004b5b90 in panic (fmt=3D0xffff000000cd5000
<sysctl___kern_racct_rctl_throttle_pct+104> "") at
/root/freebsd/sys/kern/kern_shutdown.c:892
#4  0xffff000000505bbc in kdb_sysctl_panic (oidp=3D0xffff000000cdd7f8
<sysctl___debug_kdb_panic>, arg1=3D<optimized out>, arg2=3D<optimized out>,
req=3D0xffff00010eb496e0) at /root/freebsd/sys/kern/subr_kdb.c:219
#5  0xffff0000004c7988 in sysctl_root_handler_locked
(oid=3Doid@entry=3D0xffff000000cdd7f8 <sysctl___debug_kdb_panic>,
arg1=3Darg1@entry=3D0x0, arg2=3Darg2@entry=3D0, req=3Dreq@entry=3D0xffff000=
10eb496e0,
tracker=3Dtracker@entry=3D0xffff00010eb49668) at
/root/freebsd/sys/kern/kern_sysctl.c:199
#6  0xffff0000004c6ce8 in sysctl_root (oidp=3D<optimized out>, arg1=3D0x0,
arg1@entry=3D0xffff00010eb497a0, arg2=3D0, arg2@entry=3D3,
req=3Dreq@entry=3D0xffff00010eb496e0) at /root/freebsd/sys/kern/kern_sysctl=
.c:2405
#7  0xffff0000004c736c in userland_sysctl (td=3Dtd@entry=3D0xffff0001433032=
c0,
name=3Dname@entry=3D0xffff00010eb497a0, namelen=3D<optimized out>, old=3D<o=
ptimized
out>, oldlenp=3D<optimized out>, inkernel=3D<optimized out>,
inkernel@entry=3D246716288, new=3D<optimized out>, newlen=3D<optimized out>,
retval=3D0xffff00010eb49798, flags=3D0)
    at /root/freebsd/sys/kern/kern_sysctl.c:2562
#8  0xffff0000004c7204 in sys___sysctl (td=3D0xffff0001433032c0,
uap=3D0xffff0001433036c0) at /root/freebsd/sys/kern/kern_sysctl.c:2435
#9  0xffff00000088149c in syscallenter (td=3D0xffff0001433032c0) at
/root/freebsd/sys/arm64/arm64/../../kern/subr_syscall.c:189
#10 svc_handler (td=3D0xffff0001433032c0, frame=3D<optimized out>) at
/root/freebsd/sys/arm64/arm64/trap.c:198
#11 do_el0_sync (td=3D0xffff0001433032c0, frame=3D<optimized out>) at
/root/freebsd/sys/arm64/arm64/trap.c:658
#12 <signal handler called>
#13 0x0000764dd193503c in ?? ()
#14 0x0000764dc8cc1f94 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

jhb@ suggests that there might be a problem with the debug info file.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283159-227-tA3gnSYyYP>