Date: Thu, 29 Jun 2023 22:05:17 +0200 From: Juraj Lutter <otis@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: nvme related(?) panic on recent -CURRENT Message-ID: <FBBAEB64-243D-4AF8-9CC6-E503A675FF4D@FreeBSD.org> In-Reply-To: <CANCZdfpbcQRsdFzKfRNWnZjn1Hv7v%2Bkq49H5QDcjyctEmGKavg@mail.gmail.com> References: <664978DE-B510-4C14-A559-541C3AB00D50@FreeBSD.org> <CANCZdfpbcQRsdFzKfRNWnZjn1Hv7v%2Bkq49H5QDcjyctEmGKavg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On 29 Jun 2023, at 22:01, Warner Losh <imp@bsdimp.com> wrote: > > What's the panic string? I don’t have any, even savecore did not worked. I’ve left a “cu” session to the VM’s console running under tmux and should it reappear, I can grab it. otis — Juraj Lutter otis@FreeBSD.orghelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FBBAEB64-243D-4AF8-9CC6-E503A675FF4D>