Date: Thu, 11 Aug 2016 17:48:21 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: David Wolfskill <david@catwhisker.org>, Adrian Chadd <adrian.chadd@gmail.com>, "stable@freebsd.org" <stable@freebsd.org> Subject: Re: Panic in stable/11 (amd64) @r303903: page fault while in kernel mode Message-ID: <CAJ-VmonLmpgV1Max-V2nZ5wi-RSa6rQ2QGaMQf6GO%2BS3XEF05g@mail.gmail.com> In-Reply-To: <20160811234250.GC1112@albert.catwhisker.org> References: <20160810165458.GB1112@albert.catwhisker.org> <570bda1e-d4d7-42dc-6037-7c321ba9e97d@FreeBSD.org> <CAJ-Vmon6Rak07ux%2BZX8ySnxkgn5Sv9Jtcus4SSv=J_sXTWQ%2BgQ@mail.gmail.com> <20160811234250.GC1112@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Just pop open the crashdump and "print *ifp" in the last stack frame before trap. -a On 11 August 2016 at 16:42, David Wolfskill <david@catwhisker.org> wrote: > On Thu, Aug 11, 2016 at 04:37:26PM -0700, Adrian Chadd wrote: >> Eep. Is this anotehr case where there's a race and ifp is NULL or the >> ll pointer for ifp is NULL or use-after-free'd? > > I don't know, but it's the only panic of a similar nature I've seen -- > though since on any given day, I'm usually running FreeBSD freshly-built > that morning, "trends" might be a little more difficult to determine. > >> I remember bumping into these here and there because we don't seem to >> have a well defined lifecycle for lladdr access. ;( > > Well, you're quite welcome to grab the crash data & poke around, or tell > me where to look, and I'll do so..... > >> ... >> >> Gory details (both "normal" and gzipped, and including the crash >> >> dump and crashinfo) are in >> >> <http://www.catwhisker.org/~david/FreeBSD/stable_11/2016.08.10/>. >> ... > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Those who would murder in the name of God or prophet are blasphemous cowards. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonLmpgV1Max-V2nZ5wi-RSa6rQ2QGaMQf6GO%2BS3XEF05g>