Date: Sat, 25 Jan 2020 09:41:06 +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.094106.153690936170588907.ish@amail.plala.or.jp> In-Reply-To: <20200125.065317.610346733356820759.ish@amail.plala.or.jp> References: <ae6669a2-4822-d2fd-f227-c9c41f0a8a99@selasky.org> <20200124165726.GN1268@FreeBSD.org> <20200125.065317.610346733356820759.ish@amail.plala.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
>> H> >>> My machine was panicked on r357061 with in_epoch in netisr.c. >> H> >>> I can not capture screen. >> H> >> >> H> >> 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 committing >> 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. > > Now, I'm doing buildworld/buildkernel on r357093 with D23347 and D23348. Hi. t357093 with D23347 and D23348 was panicked. Screenshot is https://www.ish.org/files/panic-r357093+D23347+D23348.jpeg -- Masachika ISHIZUKA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200125.094106.153690936170588907.ish>