Date: Tue, 20 Oct 2015 11:29:09 -0700 From: John Baldwin <jhb@freebsd.org> To: freebsd-drivers@freebsd.org Cc: Matthew Ahrens <mahrens@delphix.com>, Marc Goroff <Marc.Goroff@quorum.net> Subject: Re: NVME panic Message-ID: <13519442.8oMl4uzFz0@ralph.baldwin.cx> In-Reply-To: <CAJjvXiF_esAC0sUVPkjfhfsFizzkq02A_GERA6ebLgni_pOBBw@mail.gmail.com> References: <CAJjvXiF_esAC0sUVPkjfhfsFizzkq02A_GERA6ebLgni_pOBBw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, October 14, 2015 09:52:53 PM Matthew Ahrens wrote: > I'm not sure if this is the right place to ask, so please redirect me if > necessary. > > An associate of mine (cc'd) is hitting panics in the NVME driver when using > FreeBSD 10.2-RELEASE. He's using the NVME driver for ZFS cache (L2ARC) and > log (ZIL/SLOG) devices, and he wasn't seeing any problems with it on 10.1. > He filed a bug but I was wondering if there's anything more we can do to > bring this to the attention of someone who might be able to help with it. > > The bug is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203746, and > the panic is in nvme_bio_child_done(). Jim Harris works on the team at Intel that maintains nvme(4). I've added him to the bug report. On first glance it seems like bio_driver1 might have been NULL in the completed request? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13519442.8oMl4uzFz0>