Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2017 07:19:39 +0100
From:      Jim <BM-2cWfdfG5CJsquqkJyry7hZT9LypbSEWEkQ@bitmessage.ch>
To:        Mark Johnston <markj@FreeBSD.org>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Panic in nd6_prefix_offlink()
Message-ID:  <20170111071939.9e3983da5cc61cfe658201da@bitmessage.ch>
In-Reply-To: <20170108184815.GB34440@raichu>
References:  <20170107201119.22d9ceff88e935c2b3f072a1@bitmessage.ch> <20170108184815.GB34440@raichu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Jan 2017 10:48:15 -0800
Mark Johnston <markj@FreeBSD.org> wrote:

> On Sat, Jan 07, 2017 at 08:11:19PM +0100, Jim wrote:
> > Hello,
> > 
> > I observe frequent crashes on Beagle Bone Black running CURRENT r311106 at home.
> > My home LAN is connected to DSL provider. The CPE router gets assigned IPv6 address (ds-lite) and advertises prefix/route to the LAN.
> > Every night the DSL connection is terminated by provider. Upon connection is reestablished the new IPv6 prefix is assigned to router and then advertised to LAN. 
> > This event seems to cause kernel panic on Beagelebone board which goes to db> prompt.
> > 
> > Backtrace shows:  nd6_timer() -> nd6_prefix_offlink() -> witness_assert() -> vpanic() 
> > Here is the backtrace:
> 
> Thanks for the report. This should be addressed by r311695.



Confirm that the problem is resolved.

Thank you.

-- 
Jim




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