Date: Thu, 22 Mar 2018 14:00:02 +0100 From: Olivier Houchard <cognet@ci0.org> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: Adrian Chadd <adrian@freebsd.org>, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: crash with ipfw nat on mips32 Message-ID: <20180322130002.GA65574@ci0.org> In-Reply-To: <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru> References: <CAJ-Vmok5G93o4O6Ltb6qiGOKZ=LuxD4YDzvh_tXqmK1XYn%2BiQQ@mail.gmail.com> <f51a9986-d577-649e-d781-28d0f4d06a1d@yandex.ru> <CAJ-Vmok_kpLj6gjR8ScJAT5ySf_p9746g7T%2B8vZwSgyL0G2mrg@mail.gmail.com> <70a569db-fa82-f2f6-61ea-a0d1a3dd9dae@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote: > On 22.03.2018 10:31, Adrian Chadd wrote: > > Erk. I'll go see if I can figure out what's going on. > > > > Thanks! This is really quite grr-y. > >>> 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> > >> > >> this is not NAT related, it is ipfw's dynamic states. > >> I'm not sure, but this is seems related to ConcurrencyKit. > > It looks like CK doesn't declare support for mips. > Probably we need to make compat shim, that uses old implementation for > platforms, that are not supported by CK. > Hi, mips should be supported by using the compiler builtins, as is riscv. If there is a crash, it is definitively a bug. Can you guys tell me which CK function dies that badly ? Regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180322130002.GA65574>