Date: Sat, 12 Aug 2023 06:23:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273081] aarch64 kyua run on 14.0-ALPHA1: sys/net/if_lagg_test:status_stress got "Fatal data abort" panic Message-ID: <bug-273081-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273081 Bug ID: 273081 Summary: aarch64 kyua run on 14.0-ALPHA1: sys/net/if_lagg_test:status_stress got "Fatal data abort" panic Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: marklmi26-fbsd@yahoo.com I booted a Windows Dev Kit 2023 via a Rock64 snapshot of 14.0-ALPHA1 dd'd to USB media: # uname -apKU FreeBSD generic 14.0-ALPHA1 FreeBSD 14.0-ALPHA1 aarch64 1400094 #0 main-n264678-136fc495615f: Fri Aug 11 12:22:32 UTC 2023=20=20=20=20 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm= 64 aarch64 1400094 1400094 I logged in and tried: # /usr/bin/kyua test -k /usr/tests/Kyuafile sys/net/if_lagg_test:status_str= ess It panicked, replicating the prior report for a personal build, see: https://lists.freebsd.org/archives/freebsd-current/2023-August/004182.html Unread portion of the kernel message buffer: (dump_iface + 0x2c0) elr: 0xffff00000046e92c (sx_sysinit + 0x8) spsr: 0x0000000000400045 far: 0x0000000000000001 esr: 0x0000000096000004 panic: vm_fault failed: 0xffff00000046e92c error 1 cpuid =3D 0 time =3D 1691761822 KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x30 vpanic() at vpanic+0x13c panic() at panic+0x44 data_abort() at data_abort+0x358 handle_el1h_sync() at handle_el1h_sync+0x14 --- exception, esr 0x96000004 sx_sysinit() at sx_sysinit+0x8 dump_iface() at dump_iface+0x2bc dump_iface() at dump_iface+0x2bc dump_cb() at dump_cb+0x18 if_foreach_sleep() at if_foreach_sleep+0x254 rtnl_handle_getlink() at rtnl_handle_getlink+0xec rtnl_handle_message() at rtnl_handle_message+0x19c nl_taskqueue_handler() at nl_taskqueue_handler+0x5dc taskqueue_run_locked() at taskqueue_run_locked+0x17c taskqueue_thread_loop() at taskqueue_thread_loop+0xc8 fork_exit() at fork_exit+0x74 fork_trampoline() at fork_trampoline+0x14 KDB: enter: panic 0x0000000000000000 in ?? () (kgdb) #0 0x0000000000000000 in ?? () #1 <unavailable> in ?? () Backtrace stopped: not enough registers or memory available to unwind furth= er Notably the prior week's snapshot on a RPi4B did not replicate the panic. Again see: https://lists.freebsd.org/archives/freebsd-current/2023-August/004182.html --=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-273081-227>