Date: Sat, 3 May 2014 15:31:11 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Fabian Keil" <freebsd-listen@fabiankeil.de>, "FreeBSD-Current" <freebsd-current@FreeBSD.org>, "LI Xin" <delphij@delphij.net> Subject: Re: Fatal double fault in ZFS with yesterday's CURRENT Message-ID: <FE7EC65BCB3D44E2B9864D48346CA638@multiplay.co.uk> References: <20140503102923.6fadd904@fabiankeil.de>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Fabian Keil" <freebsd-listen@fabiankeil.de> > 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/ > > 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. > 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. 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. 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. Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE7EC65BCB3D44E2B9864D48346CA638>