Date: Fri, 24 Jan 2020 09:59:26 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Masachika ISHIZUKA <ish@amail.plala.or.jp>, current@freebsd.org, Gleb Smirnoff <glebius@FreeBSD.org> Subject: Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694 Message-ID: <7f44262b-eab6-f02a-0168-365add2d0ad9@selasky.org> In-Reply-To: <20200124.174103.1023461056313815929.ish@amail.plala.or.jp> References: <EB09DB96-1717-4560-AFC5-52C8AEB5CC5B@van-laarhoven.org> <3041901579770984@myt4-4d473ee472d6.qloud-c.yandex.net> <20200124.162344.1430316126325877949.ish@amail.plala.or.jp> <20200124.174103.1023461056313815929.ish@amail.plala.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-01-24 09:41, Masachika ISHIZUKA wrote: >>> 21.01.2020, 20:10, "Nick Hibma" <nick@van-laarhoven.org>: >>>> That (with the return added, thanks Cy) worked like a charm. >>> Got committed in r357038. >>> Thank you for the report! >> >> Hi. >> >> My machine was panicked on r357061 with in_epoch in netisr.c. >> I can not capture screen. > > Screenshot was uploaded to https://www.ish.org/files/panic-r357061.jpeg > Looks like the WLAN subsystem needs some patches for EPOCH(). Gleb, did you do a "grep -r" for relevant functions before committing the recent EPOCH changes? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7f44262b-eab6-f02a-0168-365add2d0ad9>