From owner-freebsd-fs@FreeBSD.ORG Wed Jul 29 11:42:21 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F238A106566C; Wed, 29 Jul 2009 11:42:20 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CD8E78FC14; Wed, 29 Jul 2009 11:42:19 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA00438; Wed, 29 Jul 2009 14:42:17 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A703598.8080809@icyb.net.ua> Date: Wed, 29 Jul 2009 14:42:16 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090630) MIME-Version: 1.0 To: Thomas Backman References: <20090727072503.GA52309@jpru.ffm.jpru.de> <4A6E06E6.9030300@mail.zedat.fu-berlin.de> <4A6EC9E2.5070200@icyb.net.ua> <20090729084723.GD1586@garage.freebsd.pl> <4A7030B6.8010205@icyb.net.ua> In-Reply-To: <4A7030B6.8010205@icyb.net.ua> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, FreeBSD current , Pawel Jakub Dawidek Subject: Re: zfs: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 11:42:21 -0000 on 29/07/2009 14:21 Andriy Gapon said the following: > Your panics are superficially similar but seem to be different. > But it is hard to tell as function argument values are not available in your > backtraces for the interesting calls. > One difference that I see is that your panics happen one level below _sx_xlock, in > sx_xlock_hard and sx argument value appears to be far from NULL > (0xffffff0043557d50) - in the panic that started this thread it was near NULL. > Another difference is that you panics do not involve zfs_znode_dmu_fini and > mu_buf_update_user, in your case sx_xlock is called directly from > zfs_freebsd_reclaim. So it must a problem with a different lock. BTW, have you tried to reproduce the problem with INVARIANTS enabled? Do you have crashdumps with debugging symbols? -- Andriy Gapon