Date: Mon, 5 Oct 2020 15:20:07 -0600 From: Warner Losh <imp@bsdimp.com> To: Alexander Motin <mav@freebsd.org> Cc: Xin LI <d@delphij.net>, FreeBSD Current <freebsd-current@freebsd.org>, Warner Losh <imp@freebsd.org> Subject: Re: GPF on boot with devmatch Message-ID: <CANCZdfp_djyU_-UkRHy1eZEu_XLekc%2BYuA2=9k74=rbJFR3S0A@mail.gmail.com> In-Reply-To: <02fa309e-9467-f741-8092-974bfc145c9a@FreeBSD.org> References: <02fa309e-9467-f741-8092-974bfc145c9a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 5, 2020 at 12:36 PM Alexander Motin <mav@freebsd.org> wrote: > I can add that we've received report about identical panic on FreeBSD > releng/12.2 of r365436, AKA TrueNAS 12.0-RC1: > https://jira.ixsystems.com/browse/NAS-107578 . So it looks a) pretty > rate (one report from thousands of early adopters and none in our lab), > and b) it is in stable/12 too, not only head. > Thanks! I'll see if I can recreate here.... But we're accessing the sysctl tree from devmatch to get some information, which should always be OK (the fact that it isn't suggests either a bug in some driver leaving bad pointers, or some race or both)... It would be nice to know which nodes they were, or to have a kernel panic I can look at... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp_djyU_-UkRHy1eZEu_XLekc%2BYuA2=9k74=rbJFR3S0A>