Bug 270816 - kernel panic in sym_hipd.c
Summary: kernel panic in sym_hipd.c
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.4-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2023-04-13 13:42 UTC by L4rS
Modified: 2023-04-20 07:19 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description L4rS 2023-04-13 13:42:18 UTC 
We randomly get a kernel panic on our freebsd 12.4 VMs:

Apr 10 07:28:17.012 myvm kernel: assertion "cp->host_status == HS_COMPLETE" failed: file "/usr/src/sys/dev/sym/sym_hipd.c", line 7262
Apr 10 07:28:17.012 myvm kernel: assertion "cp->host_status == HS_COMPLETE" failed: file "/usr/src/sys/dev/sym/sym_hipd.c", line 7262
Apr 10 07:28:17.012 myvm kernel: = 6
Apr 10 07:28:17.012 myvm kernel: = 6
Apr 10 07:28:17.012 myvm kernel: = 1681104239
Apr 10 07:28:17.012 myvm kernel: = 1681104239
Apr 10 07:28:17.012 myvm kernel: stack backtrace:
Apr 10 07:28:17.012 myvm kernel: stack backtrace:
Apr 10 07:28:17.012 myvm kernel: at db_trace_self_wrapper+0x2b/frame 0xfffffe009822c2a0
Apr 10 07:28:17.012 myvm kernel: at db_trace_self_wrapper+0x2b/frame 0xfffffe009822c2a0
Apr 10 07:28:17.012 myvm kernel: at vpanic+0x178/frame 0xfffffe009822c2f0
Apr 10 07:28:17.012 myvm kernel: at vpanic+0x178/frame 0xfffffe009822c2f0
Apr 10 07:28:17.012 myvm kernel: at panic+0x43/frame 0xfffffe009822c350
Apr 10 07:28:17.012 myvm kernel: at panic+0x43/frame 0xfffffe009822c350
Apr 10 07:28:17.012 myvm kernel: at sym_intr1+0xc46/frame 0xfffffe009822c3b0
Apr 10 07:28:17.012 myvm kernel: at sym_intr1+0xc46/frame 0xfffffe009822c3b0
Apr 10 07:28:17.012 myvm kernel: at sym_intr+0x33/frame 0xfffffe009822c3d0
Apr 10 07:28:17.012 myvm kernel: at sym_intr+0x33/frame 0xfffffe009822c3d0
Apr 10 07:28:17.012 myvm kernel: at ithread_loop+0x1d0/frame 0xfffffe009822c430
Apr 10 07:28:17.012 myvm kernel: at ithread_loop+0x1d0/frame 0xfffffe009822c430
Apr 10 07:28:17.018 myvm kernel: at fork_exit+0x83/frame 0xfffffe009822c470
Apr 10 07:28:17.018 myvm kernel: at fork_exit+0x83/frame 0xfffffe009822c470
Apr 10 07:28:17.018 myvm kernel: at fork_trampoline+0xe/frame 0xfffffe009822c470
Apr 10 07:28:17.018 myvm kernel: at fork_trampoline+0xe/frame 0xfffffe009822c470
Apr 10 07:28:17.018 myvm kernel: trap 0, rip = 0, rsp = 0, rbp = 0 ---
Apr 10 07:28:17.018 myvm kernel: trap 0, rip = 0, rsp = 0, rbp = 0 ---
Apr 10 07:28:17.018 myvm kernel: enter: panic
Apr 10 07:28:17.018 myvm kernel: enter: panic

Unfortunately I'm not able to trigger the panic.
Comment 1 L4rS 2023-04-20 07:19:58 UTC 
Are there any further information required? Just let me know if I can provide any information, or do some tests.