From owner-freebsd-fs@freebsd.org Tue Nov 21 09:49:11 2017 Return-Path: Delivered-To: freebsd-fs@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 8743CDE923C for ; Tue, 21 Nov 2017 09:49:11 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CBB5670F8 for ; Tue, 21 Nov 2017 09:49:10 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f42.google.com with SMTP id d10so2291968lfj.7 for ; Tue, 21 Nov 2017 01:49:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dx1dDGhVOTVSSjJEL29QblZLuPTIf2QNp+1bl6pav8A=; b=KNQyqtxgl14yHefkvhgL7RC1mubdXZqJjpPm4+Q71NKbUE6Tt9wXHuWoMi+P3hqj7v sZPV8FQ1pQ+d+Ne6Jwp1MvKE4srvU2ie9tjunoJvHMnXhGISE8Pftv9LXiCKRN3quqyR MZJdKKSBJT4jmRVJNZR38AgpdYo14KmJn70KA694ZWXbtSAbosyV9sRHcCDzPMUNfSK7 ztWBjIvhtjS1ybaTMw5vGpnLvY0fm9R4ljNbeR8WAT22VE7NGZYjoyBQTPG8gNjyphrX xviCoTqdpPw4eUrann3tgGFkMIpGKW6eNQzzlK1bxB7tOs2CY/r9SzlA0dQRvA3TlX89 vfyA== X-Gm-Message-State: AJaThX4nBfsCIrXb3h7usNBK5Klvf0Thf5uUwCLxM+F5yySIlj8uBzo/ AsANH0L3tKVev9l46nMQIqKJh6stbvg= X-Google-Smtp-Source: AGs4zMYT1Sl4WVSiBQ7v7tI2DrqmVycUHrgROHrCZLUtJLkq/kdbTDIV3C7YKmAcVvmhnFjXt3ok0A== X-Received: by 10.25.87.147 with SMTP id l141mr197151lfb.111.1511257743133; Tue, 21 Nov 2017 01:49:03 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id 17sm3045911ljh.73.2017.11.21.01.49.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 01:49:02 -0800 (PST) Subject: Re: zio_done panic in 10.3 To: Shiva Bhanujan , "freebsd-fs@freebsd.org" References: <3A5A10BE32AC9E45B4A22F89FC90EC0701C367D3D1@QLEXC01.Quorum.local> From: Andriy Gapon Message-ID: <5021a016-9193-b626-78cf-54ffa3929e22@FreeBSD.org> Date: Tue, 21 Nov 2017 11:49:01 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <3A5A10BE32AC9E45B4A22F89FC90EC0701C367D3D1@QLEXC01.Quorum.local> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2017 09:49:11 -0000 On 20/11/2017 22:34, Shiva Bhanujan wrote: > Hello, > > I'm getting a kernel panic in FreeBSD 10.3 p22 (r324806M). > > KDB: stack backtrace: > #0 0xffffffff80982fe0 at kdb_backtrace+0x60 > #1 0xffffffff80945cb6 at vpanic+0x126 > #2 0xffffffff80945b83 at panic+0x43 > #3 0xffffffff80d4ac6b at trap_fatal+0x36b > #4 0xffffffff80d4af6d at trap_pfault+0x2ed > #5 0xffffffff80d4a5ea at trap+0x47a > #6 0xffffffff80d305b2 at calltrap+0x8 > #7 0xffffffff8094db5d at _sx_xlock+0x5d > #8 0xffffffff81a4ccec at zio_done+0x92c > #9 0xffffffff81a486ea at zio_execute+0x10a > #10 0xffffffff80993e15 at taskqueue_run_locked+0xe5 > #11 0xffffffff809948a8 at taskqueue_thread_loop+0xa8 > #12 0xffffffff8090f13a at fork_exit+0x9a > #13 0xffffffff80d30aee at fork_trampoline+0xe > > We are doing send/receive of zfs snapshots by piping it through mbuffer and netcat. I can't seem to relate send/receive to the above backtrace. > > The closest bug that I've found w/ a panic close to the above is as follows: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?format=multiple&id=181966 > > I haven't been able to find any commits against this backtrace. Can anybody please point me to anything that might have addressed this issue? please let me know if there is any additional information that you might need. Do you have a crash dump (vmcore) ? If not, could you please get one? -- Andriy Gapon