Date: Tue, 1 Apr 2014 20:19:01 +0200 From: Idwer Vollering <vidwer@gmail.com> To: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: ZFS panic: spin lock held too long Message-ID: <CAPp9Or=Rugd0c1dGoqTtTVSFy79-4yDDTiBpinFkXJa7t1hGng@mail.gmail.com> In-Reply-To: <533A5F65.7020800@FreeBSD.org> References: <CAPp9OrnFL-bNbocA%2B%2BUqSb%2BW79QHr5=q_ZFQdod3N8SZ8=iOFQ@mail.gmail.com> <53391F6C.9070208@FreeBSD.org> <CAPp9Orm0V91pbCS=Yygd1zuFkcq6pAWbxosWSAz8jUWGX3bxEg@mail.gmail.com> <533A5F65.7020800@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Adding freebsd-hardware@ 2014-04-01 8:40 GMT+02:00 Andriy Gapon <avg@freebsd.org>: > So, this thread is stuck waiting on some CPU(s) doing TLB shootdown. > This must mean that that CPU is stuck doing something. > I can not provide exact instructions on how to find out which CPU is stuck and > what it is doing, but you could try to start with examining output of 'thread > apply all bt'. Inline output was over 200KB big, twice, so here is the output from 'thread apply all bt': http://ra.openbios.org/~idwer/freebsd/vmcore.0.kgdb_out http://ra.openbios.org/~idwer/freebsd/vmcore.1.kgdb_out
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPp9Or=Rugd0c1dGoqTtTVSFy79-4yDDTiBpinFkXJa7t1hGng>