From owner-freebsd-fs@freebsd.org Tue Oct 8 15:25:49 2019 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D59E212D1D8 for ; Tue, 8 Oct 2019 15:25:49 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46nh4s5P4Xz46Rg; Tue, 8 Oct 2019 15:25:49 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 12E7A21B2B; Tue, 8 Oct 2019 11:25:49 -0400 (EDT) Received: from imap36 ([10.202.2.86]) by compute5.internal (MEProxy); Tue, 08 Oct 2019 11:25:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=AJvxFkKnIJbs0BYkZgka7fcI+cxXouq Yacae/4P74E8=; b=ngH0Awsr1uXpmIXeLSpaHN+cba1C/6omr1EDzBTimMshnOr K/+q6omZnqtDx8p3ArolkqmhuzPIlc/NcMwsacXljcMJ7R8xxRd58zUEg3uP6q3C 4VhVenpHAWU4D/a6zlEKobyj383tNSrd6U6ctE2f9WLRYx131s5kSxIqUidTkodi hnTwhTW29W5lLLEzJfWigY8U8S/emBgPEEieDjIUG0fiMX8Pt5peo5ZIYqJ1bELU ybL+ytqvcd87NWrxkhC390Ckn4qQzbizCiw13QjmAkBNbnNhLBopH8XYveYu6psr xUIVHVKl/Fy1D/lKO0FKXvZmmVDgeKm0mBB4Dcg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=AJvxFk KnIJbs0BYkZgka7fcI+cxXouqYacae/4P74E8=; b=ABMLkapXVwanPsQKAj55Ci EuSP+dETt/fnWV2DoMQv3/J0eS+5KJM5gNkXw6F5KTwPVLQNRIyPZkPblUohAwFp BjA2mY16hbsEQ7Ju3QHDsxWLVHsufEmDaJnNXnbLLxvhfP0NM0OeEApN9tBRppDd cliGsZDl/7pQULZ4WsZ4eBXnyPPTUOCJ2CtwEhU9Quml/BsBKYyvhouFqorQPgkv s3aWImKBhPevvOmUQoVzklysa1vnl+2q4mRBjm9AxkOvs7gPsvSR1iXkjkytDJRN XRw+gdiHzzHcRXPrJOSRssjYFH/3O0j7/O13sO4sAfdgSCqU6KIJ3WX6G4kTzYug == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheelgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdgjuhhrihcurfgrnhhkohhvfdcuoeihuhhrihhpvheshihu rhhiphhvrdhnvghtqeenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucfrrghrrg hmpehmrghilhhfrhhomhephihurhhiphhvseihuhhrihhpvhdrnhgvthenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id A6441188005E; Tue, 8 Oct 2019 11:25:48 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-360-g7dda896-fmstable-20191004v2 Mime-Version: 1.0 Message-Id: <16474299-09e4-4b6f-9e12-5e04b7b4c3b6@www.fastmail.com> In-Reply-To: References: <68853b35-e202-40b9-80ad-b29bc49bb5b4@www.fastmail.com> Date: Tue, 08 Oct 2019 18:25:19 +0300 From: "Yuri Pankov" To: "Andriy Gapon" , freebsd-fs@FreeBSD.org Subject: Re: panic: Memory modified after free Content-Type: text/plain X-Rspamd-Queue-Id: 46nh4s5P4Xz46Rg X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.995,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2019 15:25:49 -0000 On Tue, Oct 8, 2019, at 10:12 AM, Andriy Gapon wrote: > On 08/10/2019 03:39, Yuri Pankov wrote: > > (posting to fs@ as backtrace suggests zfs) > > > > Started seeing the following panic (sometimes reproducible, so can't point specific revision or time range) untaring an archive over ssh into my home directory on zfs: > > > > panic: Memory modified after free 0xfffff80404cff000(4096) val=dead40de @ 0xfffff80404cff694 > > > > cpuid = 4 > > time = 1570493241 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00df912650 > > vpanic() at vpanic+0x19d/frame 0xfffffe00df9126a0 > > panic() at panic+0x43/frame 0xfffffe00df912700 > > trash_ctor() at trash_ctor+0x49/frame 0xfffffe00df912710 > > uma_zalloc_arg() at uma_zalloc_arg+0xa24/frame 0xfffffe00df9127a0 > > abd_alloc() at abd_alloc+0x152/frame 0xfffffe00df9127f0 > > arc_hdr_alloc_pabd() at arc_hdr_alloc_pabd+0x166/frame 0xfffffe00df912820 > > arc_write_ready() at arc_write_ready+0x463/frame 0xfffffe00df912860 > > zio_ready() at zio_ready+0xde/frame 0xfffffe00df9128a0 > > zio_execute() at zio_execute+0x17c/frame 0xfffffe00df9128e0 > > taskqueue_run_locked() at taskqueue_run_locked+0x10c/frame 0xfffffe00df912940 > > taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe00df912970 > > fork_exit() at fork_exit+0x84/frame 0xfffffe00df9129b0 > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00df9129b0 > > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > > > Full text dump is at https://people.freebsd.org/~yuripv/core.txt.0. > > > > Real problem or failing hardware (memory?)? > > Given a single bit difference between 0xdead40de and 0xdeadc0de, it can be > either. If the memory is not ECC, then I would assume a hardware problem first. Thank you. Laptop with non-ECC memory, which started showing those bit flips after several memtest86 runs (it didn't previously). Sorry for the noise!