Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2018 00:31:22 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        "Andrey V. Elsukov" <bu7cher@yandex.ru>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: crash with ipfw nat on mips32
Message-ID:  <CAJ-Vmok_kpLj6gjR8ScJAT5ySf_p9746g7T%2B8vZwSgyL0G2mrg@mail.gmail.com>
In-Reply-To: <f51a9986-d577-649e-d781-28d0f4d06a1d@yandex.ru>
References:  <CAJ-Vmok5G93o4O6Ltb6qiGOKZ=LuxD4YDzvh_tXqmK1XYn%2BiQQ@mail.gmail.com> <f51a9986-d577-649e-d781-28d0f4d06a1d@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Erk. I'll go see if I can figure out what's going on.

Thanks! This is really quite grr-y.



-a





On 21 March 2018 at 23:35, Andrey V. Elsukov <bu7cher@yandex.ru> wrote:
> On 22.03.2018 09:23, Adrian Chadd wrote:
>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
>> [ thread pid 11 tid 100010 ]
>> Stopped at      0
>> db> bt
>> Tracing pid 11 tid 100010 td 0x80673b40
>> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144
>> dyn_tick+0x238 (0,?,?,?) ra 80214dfc sp c1247cd0 sz 120
>> itimer_fire+0x1440 (?,?,?,?) ra 802150c0 sp c1247d48 sz 88
>> softclock+0x9c (?,?,?,?) ra 0 sp c1247da0 sz 0
>> db>
>
> Hi,
>
> this is not NAT related, it is ipfw's dynamic states.
> I'm not sure, but this is seems related to ConcurrencyKit.
>
> --
> WBR, Andrey V. Elsukov
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok_kpLj6gjR8ScJAT5ySf_p9746g7T%2B8vZwSgyL0G2mrg>