Re: Easily reproducible stable/13 kernel crash

From: Matthew Grooms <mgrooms_at_shrew.net>
Date: Fri, 11 Jun 2021 08:55:29 -0500
On 6/11/2021 8:19 AM, Herbert J. Skuhra wrote:
> On Fri, 11 Jun 2021 09:18:32 +0200, Hans Petter Selasky wrote:
>>   
>> Do you have the kernel backtrace of the resulting panic?
> #0  get_curthread () at /usr/src/sys/arm64/include/pcpu.h:68
> #1  doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:399
> #2  0xffff0000004b8c5c in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:486
> #3  0xffff0000004b91f0 in vpanic (fmt=<optimized out>, ap=...) at /usr/src/sys/kern/kern_shutdown.c:919
> #4  0xffff0000004b8fdc in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:843
> #5  0xffff0000007e86ec in data_abort (td=0xffffa00001740000, frame=0xffff0000dfbd93a0, esr=2516582406, far=<optimized out>, lower=0) at /usr/src/sys/arm64/arm64/trap.c:337
> #6  <signal handler called>
> #7  counter_u64_read_one (p=<optimized out>, cpu=0) at /usr/src/sys/arm64/include/counter.h:45
> #8  counter_u64_fetch_inline (p=<optimized out>) at /usr/src/sys/arm64/include/counter.h:56
> #9  counter_u64_fetch (c=<optimized out>) at /usr/src/sys/kern/subr_counter.c:57
> #10 sysctl_handle_counter_u64 (oidp=0xffff000000b25820 <sysctl___net_inet_tcp_lro_without_m_ackcmp>, arg1=0xffff000000e4b6d8 <tcp_uncomp_total>, arg2=0, req=0xffff0000dfbd9650)
>      at /usr/src/sys/kern/subr_counter.c:80
> #11 0xffff0000004caef4 in sysctl_root_handler_locked (oid=oid_at_entry=0xffff000000b25820 <sysctl___net_inet_tcp_lro_without_m_ackcmp>,
>      arg1=arg1_at_entry=0xffff000000e4b6d8 <tcp_uncomp_total>, arg2=arg2_at_entry=0, req=req_at_entry=0xffff0000dfbd9650, tracker=tracker_at_entry=0xffff0000dfbd95d8)
>      at /usr/src/sys/kern/kern_sysctl.c:184
> #12 0xffff0000004ca354 in sysctl_root (oidp=<optimized out>, arg1=0xffff000000e4b6d8 <tcp_uncomp_total>, arg1_at_entry=0xffff0000dfbd9720, arg2=0, arg2_at_entry=5, req=<optimized out>,
>      req_at_entry=0xffff0000dfbd9650) at /usr/src/sys/kern/kern_sysctl.c:2261
> #13 0xffff0000004ca948 in userland_sysctl (td=<optimized out>, td_at_entry=0xffffa00001740000, name=<optimized out>, name_at_entry=0xffff0000dfbd9720, namelen=<optimized out>,
>      old=<optimized out>, oldlenp=<optimized out>, inkernel=<optimized out>, new=<optimized out>, newlen=<optimized out>, retval=0xffff0000dfbd9718, flags=0)
>      at /usr/src/sys/kern/kern_sysctl.c:2418
> #14 0xffff0000004ca77c in sys___sysctl (td=0xffffa00001740000, uap=0xffffa000017403e8) at /usr/src/sys/kern/kern_sysctl.c:2291
> #15 0xffff0000007e7d38 in syscallenter (td=0xffffa00001740000) at /usr/src/sys/arm64/arm64/../../kern/subr_syscall.c:189
> #16 svc_handler (td=0xffffa00001740000, frame=<optimized out>) at /usr/src/sys/arm64/arm64/trap.c:187
> #17 do_el0_sync (td=0xffffa00001740000, frame=<optimized out>) at /usr/src/sys/arm64/arm64/trap.c:506
> #18 <signal handler called>
> #19 0x00000000403d15ec in ?? ()
> #20 0x0000000040353770 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thanks for providing this. I started a debug build before crashing out 
last night. Waking up with a patch ready to test was super awesome :)

-Matthew
Received on Fri Jun 11 2021 - 13:55:29 UTC

Original text of this message