Re: nvme related(?) panic on recent -CURRENT
- Reply: Juraj Lutter : "Re: nvme related(?) panic on recent -CURRENT"
- In reply to: Juraj Lutter : "nvme related(?) panic on recent -CURRENT"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 29 Jun 2023 20:01:16 UTC
What's the panic string? On Thu, Jun 29, 2023, 1:47 PM Juraj Lutter <otis@freebsd.org> wrote: > With recent -current, following occured: > > db> bt > Tracing pid 0 tid 100063 td 0xfffffe00c5c35e40 > kdb_enter() at kdb_enter+0x32/frame 0xfffffe00c5e31c90 > vpanic() at vpanic+0x181/frame 0xfffffe00c5e31ce0 > panic() at panic+0x43/frame 0xfffffe00c5e31d40 > nvme_ctrlr_identify() at nvme_ctrlr_identify+0x10e/frame 0xfffffe00c5e31d90 > nvme_ctrlr_start() at nvme_ctrlr_start+0x91/frame 0xfffffe00c5e31e10 > nvme_ctrlr_reset_task() at nvme_ctrlr_reset_task+0xec/frame > 0xfffffe00c5e31e40 > taskqueue_run_locked() at taskqueue_run_locked+0x182/frame > 0xfffffe00c5e31ec0 > taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame > 0xfffffe00c5e31ef0 > fork_exit() at fork_exit+0x7d/frame 0xfffffe00c5e31f30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00c5e31f30 > --- trap 0, rip = 0, rsp = 0, rbp = 0 — > > machine is a bhyve guest. > > otis > > > — > Juraj Lutter > XMPP: juraj (at) lutter.sk > GSM: +421907986576 > > >