On Wed, 17 Apr 2019 12:05+0200, Trond Endrestøl wrote:
> On Wed, 17 Apr 2019 12:41+0300, Andrey V. Elsukov wrote:
>
> > On 15.04.2019 16:31, Trond Endrestøl wrote:
> > > Has anyone else witnessed a panic during reboot involving
> > > softclock_call_cc(),
On Wed, 17 Apr 2019 12:41+0300, Andrey V. Elsukov wrote:
> On 15.04.2019 16:31, Trond Endrestøl wrote:
> > Has anyone else witnessed a panic during reboot involving
> > softclock_call_cc(), nd6_timer(), and nd6_dad_start()?
> >
> > The stack trace
On 15.04.2019 16:31, Trond Endrestøl wrote:
> Has anyone else witnessed a panic during reboot involving
> softclock_call_cc(), nd6_timer(), and nd6_dad_start()?
>
> The stack trace goes more or less like this:
>
> db_trace_self_wrapper()
> vpanic()
> panic()
> trap_
On Mon, 15 Apr 2019 15:31+0200, Trond Endrestøl wrote:
> Has anyone else witnessed a panic during reboot involving
> softclock_call_cc(), nd6_timer(), and nd6_dad_start()?
>
> The stack trace goes more or less like this:
>
> db_trace_self_wrapper()
> vpanic()
> panic
Hi,
Has anyone else witnessed a panic during reboot involving
softclock_call_cc(), nd6_timer(), and nd6_dad_start()?
The stack trace goes more or less like this:
db_trace_self_wrapper()
vpanic()
panic()
trap_fatal()
trap()
calltrap()
nd6_dad_start()
nd6_timer()
softclock_call_cc()
softclock
