Date: Sat, 17 Feb 2018 08:15:39 -0700 From: Warner Losh <imp@bsdimp.com> To: Hans Petter Selasky <hps@selasky.org> Cc: Warner Losh <imp@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: panic in daprobedone: Unholding 4 with cnt = 0 Message-ID: <CANCZdfocEPAvfeHKqXMzwP1ooXWJgea6XRPhYJnWvoJ2nrgMcQ@mail.gmail.com> In-Reply-To: <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org> References: <fc0dc6c5-2ef4-db6b-cfa8-7868144ba6ab@selasky.org> <CANCZdfq7w%2BsTQQwRRya0kKfEwZTpmApB4jNCEZhP=93gcvzckg@mail.gmail.com> <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 17, 2018 at 8:04 AM, Hans Petter Selasky <hps@selasky.org> wrote: > On 02/17/18 15:47, Warner Losh wrote: > >> That's interesting. What did you do to get there? There's some code path >> that's unholding the periph without first holding it. I've been trying to >> find a scenario. >> >> > I just booted into single user mode with a multi-card USB reader attached. > Seems like some kind of race. Doesn't happen during normal boot. I've done that with my systems here... If you can reliably reproduce it, booting a kernel with 'options DA_TRACK_REFS=2' in the kernel config and send me the output? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfocEPAvfeHKqXMzwP1ooXWJgea6XRPhYJnWvoJ2nrgMcQ>