From owner-freebsd-current@FreeBSD.ORG Sat May 3 17:19:12 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BE24E0F for ; Sat, 3 May 2014 17:19:12 +0000 (UTC) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B1C8109E for ; Sat, 3 May 2014 17:19:11 +0000 (UTC) Received: from [84.44.154.172] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1WgdX2-00050x-Ll for freebsd-current@FreeBSD.org; Sat, 03 May 2014 19:15:24 +0200 Date: Sat, 3 May 2014 19:14:24 +0200 From: Fabian Keil To: "FreeBSD-Current" Subject: Re: Fatal double fault in ZFS with yesterday's CURRENT Message-ID: <20140503191424.16f9744b@fabiankeil.de> In-Reply-To: References: <20140503102923.6fadd904@fabiankeil.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/pHIyTFVZAXT=BiZZO2xpe75"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: FreeBSD-Current List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2014 17:19:12 -0000 --Sig_/pHIyTFVZAXT=BiZZO2xpe75 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Steven Hartland" wrote: > From: "Fabian Keil" >=20 > > After updating my laptop to yesterday's CURRENT (r265216), > > I got the following fatal double fault on boot: > > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/ > >=20 > > My previous kernel was based on r264721. > > > > I'm using a couple of custom patches, some of them are ZFS-related > > and thus may be part of the problem (but worked fine for months). > > I'll try to reproduce the panic without the patches tomorrow. > > >=20 > Your seeing a stack overflow in the new ZFS queuing code, which I > believe is being triggered by lack of support for TRIM in one of > your devices, something Xin reported to me yesterday. >=20 > I commited a fix for failing TRIM requests processing slowly last > night so you could try updating to after r265253 and see if that > helps. Thanks. The hard disk is indeed unlikely to support TRIM requests, but I can still reproduce the problem with a kernel based on r265255. > I still need to investigate the stack overflow more directly which > appears to be caused by the new zfs queuing code when things are > running slowly and there's a large backlog of IO's. > > I would be interested to know you config there so zpool layout and > hardware in the mean time. The system is a Lenovo ThinkPad R500: http://www.nycbug.org/index.cgi?action=3Ddmesgd&do=3Dview&dmesgid=3D2449 I'm booting from UFS, the panic occurs while the pool is being imported. The pool is located on a single geli-encrypted slice: fk@r500 ~ $zpool status tank pool: tank state: ONLINE scan: scrub repaired 0 in 4h11m with 0 errors on Sat Mar 22 18:25:01 2014 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ada0s1d.eli ONLINE 0 0 0 errors: No known data errors Maybe geli fails TRIM requests differently. Fabian --Sig_/pHIyTFVZAXT=BiZZO2xpe75 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlNlI/MACgkQBYqIVf93VJ1P1wCgvrfnBkZTQ3AD53bnW4GJ0dmc R8oAoIhGMoYpDswbDyy2Z0W/ITGw0I9u =aQ2W -----END PGP SIGNATURE----- --Sig_/pHIyTFVZAXT=BiZZO2xpe75--