Date: Fri, 30 Jun 2023 10:25:27 -0700 From: Chuck Tuffli <chuck@freebsd.org> To: Juraj Lutter <otis@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: nvme related(?) panic on recent -CURRENT Message-ID: <CAKAYmMKvc8msOuEdVWhsEzc5M1i7PMDt88%2BJzf0UM4-CCeV%2BfA@mail.gmail.com> In-Reply-To: <664978DE-B510-4C14-A559-541C3AB00D50@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Thu, Jun 29, 2023 at 12: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. Did bhyve log any warnings or errors? I'm curious if its NVMe emulation did something dumb or itself noticed an issue. --chuckhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKAYmMKvc8msOuEdVWhsEzc5M1i7PMDt88%2BJzf0UM4-CCeV%2BfA>