Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 May 2019 10:27:46 -0400
From:      Mark Johnston <markj@freebsd.org>
To:        current@freebsd.org
Subject:   Re: Panic after update from r347896 to r347950: panic: insanity vmem 0xffffffff81d7c840
Message-ID:  <20190518142746.GC7370@raichu>
In-Reply-To: <20190518123506.GX79998@albert.catwhisker.org>
References:  <20190518123506.GX79998@albert.catwhisker.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 18, 2019 at 05:35:06AM -0700, David Wolfskill wrote:
> This was fairly late in the transition from single- to multi-user mode:
> the NICs had been probed; em0 was determined (correctly) to have no
> link, but the wireless NIC (wlan0) hadn't associated to the AP yet.
> 
> I have placed copies of the dump and a couple of screenshots in
> http://www.catwhisker.org/~david/FreeBSD/head/r347950/
> 
> Just before the panic message, there's:
> 
> .....overwrapped tags
> 	0xffffffff81d7cc70: 0 0, 5(cursor)
> 	0xfffff800040086c8: fffffe0c1052c000 8000000, 3(free)
> 
> and then we get to:
> panic: insanity vmem 0xffffffff81d7c840

Thanks.  This should be fixed by r347955.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190518142746.GC7370>