From owner-freebsd-current@freebsd.org Tue Jun 27 14:13:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F4AFD8672B for ; Tue, 27 Jun 2017 14:13:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 86EF067EB1 for ; Tue, 27 Jun 2017 14:13:22 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA08845; Tue, 27 Jun 2017 17:13:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dPrEp-00071V-ST; Tue, 27 Jun 2017 17:13:07 +0300 Subject: Re: ZFS ABD Panic To: Shawn Webb , freebsd-current@FreeBSD.org References: <20170626003129.ao72cszn7eeccyhp@mutt-hbsd> From: Andriy Gapon Message-ID: <61824b1e-9582-b50f-a55d-5ef4731383d0@FreeBSD.org> Date: Tue, 27 Jun 2017 17:12:01 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170626003129.ao72cszn7eeccyhp@mutt-hbsd> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 14:13:24 -0000 On 26/06/2017 03:31, Shawn Webb wrote: > This is on the latest HardenedBSD 12-CURRENT on one of my servers: > > [141] panic: sleepq_add: td 0xfffff80008d20560 to sleep on wchan 0xfffff803b7d4e810 with sleeping prohibited > [141] cpuid = 5 > [141] time = 1498436043 > [141] KDB: stack backtrace: > [141] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00002fc8b0 > [141] vpanic() at vpanic+0x19c/frame 0xfffffe00002fc930 > [141] kassert_panic() at kassert_panic+0x126/frame 0xfffffe00002fc9a0 > [141] sleepq_add() at sleepq_add+0x34f/frame 0xfffffe00002fc9f0 > [141] _sx_xlock_hard() at _sx_xlock_hard+0x2a4/frame 0xfffffe00002fcaa0 > [141] _sx_xlock() at _sx_xlock+0x98/frame 0xfffffe00002fcae0 > [141] refcount_remove_many() at refcount_remove_many+0x2a/frame 0xfffffe00002fcb20 > [141] abd_return_buf() at abd_return_buf+0xe3/frame 0xfffffe00002fcb50 > [141] vdev_geom_io_intr() at vdev_geom_io_intr+0x114/frame 0xfffffe00002fcb70 > [141] g_io_schedule_up() at g_io_schedule_up+0x42/frame 0xfffffe00002fcba0 > [141] g_up_procbody() at g_up_procbody+0x6d/frame 0xfffffe00002fcbb0 > [141] fork_exit() at fork_exit+0x84/frame 0xfffffe00002fcbf0 > [141] fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00002fcbf0 Seems like another architectural incompatibility between illumos and FreeBSD. Are you able to reproduce the crash more or less reliably? -- Andriy Gapon