From nobody Sat Jun 12 14:45:24 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1E54D7CED1D for ; Sat, 12 Jun 2021 14:45:28 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G2L9N06bzz4s4H; Sat, 12 Jun 2021 14:45:27 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id z8so9165942wrp.12; Sat, 12 Jun 2021 07:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=OceQLyia35Ase2RNDb7kwyG35//4/b/PW0Jt7k3+wlo=; b=LwLX39Tw2awXXaOtH9KpMHleIP7jDN44FSeZmrOqHOzv0QANfnCCbN+xXZmUCR8AWV R7NqrcYBeSSVeC4saNVUJYbnZ/+qSGleMIoedNjMmXjmQPMbcN5FbvlLe1hN3L6ssFCb aWpXzf+eRTu0QvkgIo3D92hS/5BUG07g9tWvnJhhuq2GSZ6uPReqbrTH0uxqmiqinpkC jmpttMgFKGvhQ502Msw6MJMs6cEXjS9Rww7B+EA/P7KrapkCt3jHlarzL8KLpv+eEKfE qz2khBdvD4XIDoE08EJwJShkdk9rknwNOCQ1DNIpMNLc7xSNUh4RZpPj2YPQUKOt+8lm g4Ng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=OceQLyia35Ase2RNDb7kwyG35//4/b/PW0Jt7k3+wlo=; b=oOpvwr6265t1yNSWSs8Mz63FlZfteZFgPEDFg8nyF6rnV7BTaOpLPJydmM6HVexNOG Lt/A1WpMNrh3b8v4xawb4BlreHb2drLWoZxJjKtqY20CoqHtZJsz7VNtCq1Gpk9kg0GU 3zu34epWls0Ad55uFSrwkVsOKourSFr8mVPjdQ31BAp15HB3OhasuRrx+3S2nhHoDkXg eURN0WVj7MR81WO9W3jH0DEdscaDylBNzc+YQ27SyuDgB5gC/tnNjeMoLqWLmfBOerqp XIOR1LUbq/g/Ftg+I+goBBE/iujyMnNOoWpDu0K9CDPsOP0SLkpWCxL6yVnQ8YeXWPKw 2nIQ== X-Gm-Message-State: AOAM5335pLF9c5J4rRzm6TGtGGTLKKcnRViCIXmNcY3aFxt/kWF0fhsH 87C3uaiDpM27yn/j58SUGXjAiGL6dRM= X-Google-Smtp-Source: ABdhPJyq1SECrF4j/LsMxm3wK1gozWAM8ykEKp+mToFcjk4Sx3Pplh7pI0XGKkGLdEbdpS69aNKWCg== X-Received: by 2002:adf:8b9a:: with SMTP id o26mr9369864wra.96.1623509126680; Sat, 12 Jun 2021 07:45:26 -0700 (PDT) Received: from ernst.home (pd9e2360f.dip0.t-ipconnect.de. [217.226.54.15]) by smtp.gmail.com with ESMTPSA id z10sm9431923wmb.26.2021.06.12.07.45.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 12 Jun 2021 07:45:26 -0700 (PDT) Date: Sat, 12 Jun 2021 16:45:24 +0200 From: Gary Jennejohn To: Edward Tomasz =?ISO-8859-1?Q?Napiera=3Fa?= Cc: FreeBSD Current Subject: Re: kernel panic while copying files Message-ID: <20210612144524.7881f852@ernst.home> In-Reply-To: References: <20210607090109.08ecb130@ernst.home> <20210608084646.6a7e1bc7@ernst.home> <20210608155405.5cf0e200@ernst.home> <20210610095041.38d7597c@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4G2L9N06bzz4s4H X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, 12 Jun 2021 14:10:36 +0100 Edward Tomasz Napiera__a wrote: > On 0610T1150, Gary Jennejohn wrote: > > On Tue, 8 Jun 2021 17:54:05 +0200 > > Gary Jennejohn wrote: > > > > [big snip] > > [..] > > > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'', > > which was the penultimate commit made by trasz to clear CCBs on the stack > > after he committed 3394d4239b85b5577845d9e6de4e97b18d3dba58, the change > > to allocate CCBs in UMA. > > > > Note that I only built the kernel and not world. > > > > I tried to reset to 3394d4239b85b5577845d9e6de4e97b18d3dba58 itself, > > but without the following commits for CCBs on the stack the kernel > > paniced during startup in AHCI. > > > > Anyway, this is the minimum set of changes relevant to the uma_ccbs > > story and also results in a panic identical to the one listed above > > when I set kern.cam.da.enable_uma_ccbs=1 and turn on the external USB > > disk. > > > > So, Warner is probably right and at least the da_uma_ccbs commits > > should be reverted until more research can be done on why the panic > > happens. > > > > The ada_uma_ccbs commits do not cause any problems in my experience and > > could probably be left in the kernel. > > Thank you, I'm working on a fix. Meanwhile - does the current code > cause any problems with set kern.cam.da.enable_uma_ccbs set to 0? > If it doesn't, it probably doesn't require backing off, since 0 is > the default, and will keep being the default until bugs such as this > one are fixed. > No, with the sysctl set to 0 it works really well. I've been running it that way for several days and have transferred large amounts of data to an external USB3 disk with no problems. I didn't mention it, but I also tested the reset kernel (with INVARIANTS) with the sysctl set to 0 and the kernel did not panic. I've had ada_enable_uma_ccbs set to 1 the whole time and never saw any problems. I agree, as long as the default is 0 all the code can stay in the tree. -- Gary Jennejohn