From nobody Tue Jun 08 09:20:37 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 A456F7EB826 for ; Tue, 8 Jun 2021 09:22:05 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FzlB53mRwz3lYv; Tue, 8 Jun 2021 09:22:05 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2237526015B; Tue, 8 Jun 2021 11:21:57 +0200 (CEST) Subject: Re: kernel panic while copying files To: Mateusz Guzik , gljennjohn@gmail.com Cc: Mark Johnston , freebsd-current@freebsd.org References: <20210607090109.08ecb130@ernst.home> <20210608084646.6a7e1bc7@ernst.home> From: Hans Petter Selasky Message-ID: <7f47fcca-eafe-59c0-40ff-de3426f3b754@selasky.org> Date: Tue, 8 Jun 2021 11:20:37 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 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 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FzlB53mRwz3lYv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On 6/8/21 11:04 AM, Mateusz Guzik wrote: > Apparently caused by recent changes to CAM. > > Let me know if you want more information. Maybe you can print the *ccb being freed and figure out which device it belongs to. --HPS