Date: Tue, 8 Jun 2021 13:38:35 +0200 From: Hans Petter Selasky <hps@selasky.org> To: gljennjohn@gmail.com Cc: Mateusz Guzik <mjguzik@gmail.com>, Mark Johnston <markj@freebsd.org>, freebsd-current@freebsd.org Subject: Re: kernel panic while copying files Message-ID: <0eee2f4e-945e-3c10-8fb2-ed77e05fb83c@selasky.org> In-Reply-To: <20210608113421.5da38371@ernst.home> References: <20210607090109.08ecb130@ernst.home> <YL6Hc6XmEIIx76gt@nuc> <20210608084646.6a7e1bc7@ernst.home> <CAGudoHF72EFG6UNZFuX9LjRbWLBefFYagQtgz8j1%2BP4fi8ZOnw@mail.gmail.com> <7f47fcca-eafe-59c0-40ff-de3426f3b754@selasky.org> <20210608113421.5da38371@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/8/21 1:34 PM, Gary Jennejohn wrote: > Fields in the ccb like periph_name, unit_number and dev_name are filled > with zeroes. Smells like a double free, like the panic message indicates, but would be nice to know exactly which driver is doing this, if it is "ATA" or "UMASS", so to speak. Maybe you need to do a quick bisect, like suggested. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0eee2f4e-945e-3c10-8fb2-ed77e05fb83c>