Date: Sat, 25 Jan 2020 06:53:17 +0900 (JST) From: Masachika ISHIZUKA <ish@amail.plala.or.jp> To: glebius@freebsd.org Cc: hps@selasky.org, current@freebsd.org Subject: Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694 Message-ID: <20200125.065317.610346733356820759.ish@amail.plala.or.jp> In-Reply-To: <20200124165726.GN1268@FreeBSD.org> References: <7f44262b-eab6-f02a-0168-365add2d0ad9@selasky.org> <ae6669a2-4822-d2fd-f227-c9c41f0a8a99@selasky.org> <20200124165726.GN1268@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> H> >>> =A0=A0 My machine was panicked on r357061 with in_epoch in net= isr.c. > H> >>> =A0=A0 I can not capture screen. > H> >> > H> >> =A0=A0 Screenshot was uploaded to = > H> >> https://www.ish.org/files/panic-r357061.jpeg > H> >> > H> > = > H> > Looks like the WLAN subsystem needs some patches for EPOCH(). > H> > = > H> > Gleb, did you do a "grep -r" for relevant functions before commi= tting = > H> > the recent EPOCH changes? > H> = > H> Can you try these two patches: > H> https://reviews.freebsd.org/D23347 > H> https://reviews.freebsd.org/D23348 > = > You could just plug it with a one liner that adds IFF_NEEDSEPOCH > in ieee80211_vap_attach(). > = > Or fix ath, which I'm going to do in next five minutes. Hi. D23347 and D23348 are not fixed my problem. Now, I'm doing buildworld/buildkernel on r357093 with D23347 and D233= 48. As I'm busy to care of my old father, I'm sorry to late reply mail. -- = Masachika ISHIZUKA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200125.065317.610346733356820759.ish>