From owner-freebsd-drivers@freebsd.org Tue Oct 20 18:32:36 2015 Return-Path: Delivered-To: freebsd-drivers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 838C6A1A2C0 for ; Tue, 20 Oct 2015 18:32:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61E791B48 for ; Tue, 20 Oct 2015 18:32:36 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5F2FEB922; Tue, 20 Oct 2015 14:32:35 -0400 (EDT) From: John Baldwin To: freebsd-drivers@freebsd.org Cc: Matthew Ahrens , Marc Goroff Subject: Re: NVME panic Date: Tue, 20 Oct 2015 11:29:09 -0700 Message-ID: <13519442.8oMl4uzFz0@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-PRERELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 20 Oct 2015 14:32:35 -0400 (EDT) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2015 18:32:36 -0000 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