Date: Wed, 29 Jul 2009 14:42:16 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Thomas Backman <serenity@exscape.org> Cc: freebsd-fs@FreeBSD.org, FreeBSD current <freebsd-current@FreeBSD.org>, Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: zfs: Fatal trap 12: page fault while in kernel mode Message-ID: <4A703598.8080809@icyb.net.ua> In-Reply-To: <4A7030B6.8010205@icyb.net.ua> References: <20090727072503.GA52309@jpru.ffm.jpru.de> <4A6E06E6.9030300@mail.zedat.fu-berlin.de> <4A6EC9E2.5070200@icyb.net.ua> <20090729084723.GD1586@garage.freebsd.pl> <F4F82B3E-C119-40EF-9AA4-937052876D1E@exscape.org> <4A7030B6.8010205@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A703598.8080809>