[Bug 286819] Boot panics when KMSAN enabled on FBSD 14 stable and FBSD 14.2 release
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 286819] Boot panics when KMSAN enabled with Ethernet driver"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 16 May 2025 06:53:05 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286819
--- Comment #2 from Haresh <hareshx.sankar.raj@intel.com> ---
Hi Mark,
We still the KMSAN issue after applying the patch proposed.
Below is the log trace:
panic: MSan: uninitialized variable in 0xffffffff81232959
cpuid = 48
time = 1747376573
KDB: stack backtrace:
#0 0xffffffff8351df86 at kdb_backtrace+0x166
#1 0xffffffff8334563f at vpanic+0x66f
#2 0xffffffff83344fcd at panic+0x1dd
#3 0xffffffff8352d849 at __msan_warning+0x219
#4 0xffffffff81232959 at em_newitr+0x1549
#5 0xffffffff812723b2 at em_msix_que+0x172
#6 0xffffffff83ac4a57 at iflib_fast_intr_rxtx+0xe7
#7 0xffffffff831c6c44 at intr_event_handle+0x3e4
#8 0xffffffff84fbf04b at intr_execute_handlers+0x1bb
#9 0xffffffff8551fbd0 at lapic_handle_intr+0x190
#10 0xffffffff85000a61 at Xapic_isr1+0xe1
#11 0xffffffff84fb01c5 at cpu_idle_acpi+0xf5
#12 0xffffffff84fb04d7 at cpu_idle+0x2d7
#13 0xffffffff83480a5a at sched_idletd+0x62a
#14 0xffffffff831b4116 at fork_exit+0x266
#15 0xffffffff8500077e at fork_trampoline+0xe
kgdb backtrace:
(kgdb) bt
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
#1 doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:405
#2 0xffffffff83343a0a in kern_reboot (howto=howto@entry=260) at
/usr/src/sys/kern/kern_shutdown.c:523
#3 0xffffffff83345877 in vpanic (fmt=fmt@entry=0xffffffff85688718 "MSan:
uninitialized variable in %p",
ap=ap@entry=0xfffffe0472120450) at /usr/src/sys/kern/kern_shutdown.c:967
#4 0xffffffff83344fcd in panic (fmt=0xffffffff85688718 "MSan: uninitialized
variable in %p")
at /usr/src/sys/kern/kern_shutdown.c:891
#5 0xffffffff8352d849 in kmsan_report_inline (orig=0, pc=18446744071581149529)
at /usr/src/sys/kern/subr_msan.c:246
#6 __msan_warning (origin=0) at /usr/src/sys/kern/subr_msan.c:711
#7 0xffffffff81232959 in em_newitr (sc=sc@entry=0xfffffe01a9bf8000,
que=que@entry=0xfffffe01abe00000,
txr=txr@entry=0xfffffe01abf8a018, rxr=rxr@entry=0xfffffe01abe00018) at
/usr/src/sys/dev/e1000/if_em.c:1713
#8 0xffffffff812723b2 in em_msix_que (arg=arg@entry=0xfffffe01abe00000) at
/usr/src/sys/dev/e1000/if_em.c:1909
#9 0xffffffff83ac4a57 in iflib_fast_intr_rxtx (arg=<optimized out>) at
/usr/src/sys/net/iflib.c:1598
#10 0xffffffff831c6c44 in intr_event_handle (ie=ie@entry=0xfffffe01a9add200,
frame=frame@entry=0xfffffe0472120ab0)
at /usr/src/sys/kern/kern_intr.c:1389
#11 0xffffffff84fbf04b in intr_execute_handlers (isrc=0xfffffe01abfb6880,
frame=frame@entry=0xfffffe0472120ab0)
at /usr/src/sys/x86/x86/intr_machdep.c:354
#12 0xffffffff8551fbd0 in lapic_handle_intr (vector=49,
frame=0xfffffe0472120ab0) at /usr/src/sys/x86/x86/local_apic.c:1287
#13 <signal handler called>
#14 0xffffffff80b14671 in acpi_cpu_idle (sbt=sbt@entry=4169159518) at
/usr/src/sys/dev/acpica/acpi_cpu.c:1167
#15 0xffffffff84fb01c5 in cpu_idle_acpi (sbt=sbt@entry=4169159518) at
/usr/src/sys/x86/x86/cpu_machdep.c:590
#16 0xffffffff84fb04d7 in cpu_idle (busy=busy@entry=0) at
/usr/src/sys/x86/x86/cpu_machdep.c:679
#17 0xffffffff83480a5a in sched_idletd (dummy=<optimized out>) at
/usr/src/sys/kern/sched_ule.c:3061
#18 0xffffffff831b4116 in fork_exit (callout=0xffffffff83480430 <sched_idletd>,
arg=0x0, frame=0xfffffe0472120f40)
at /usr/src/sys/kern/kern_fork.c:1153
#19 <signal handler called>
(kgdb) list *0xffffffff81232959
0xffffffff81232959 is in em_newitr (/usr/src/sys/dev/e1000/if_em.c:1713).
1708 else if ((packets < 10) ||
1709 (bytes_per_packet > 1200))
1710 nextlatency = itr_latency_bulk;
1711 else if (packets > 35)
1712 nextlatency =
itr_latency_lowest;
1713 } else if (bytes_per_packet > 2000) {
1714 nextlatency = itr_latency_bulk;
1715 } else if (packets < 3 && bytes < 512) {
1716 nextlatency = itr_latency_lowest;
1717 }
--
You are receiving this mail because:
You are the assignee for the bug.