Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

From: Gleb Smirnoff <glebius_at_freebsd.org>
Date: Fri, 24 Jan 2020 08:57:26 -0800
On Fri, Jan 24, 2020 at 01:18:26PM +0100, Hans Petter Selasky wrote:
H> On 2020-01-24 09:59, Hans Petter Selasky wrote:
H> > On 2020-01-24 09:41, Masachika ISHIZUKA wrote:
H> >>>> 21.01.2020, 20:10, "Nick Hibma" <nick_at_van-laarhoven.org>:
H> >>>>> That (with the return added, thanks Cy) worked like a charm.
H> >>>> Got committed in r357038.
H> >>>> Thank you for the report!
H> >>>
H> >>>    Hi.
H> >>>
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.

P.S. Answering your other email. Of course I did grep. Some things are
untrivial and sometimes sweeping over all collection of drivers doesn't
go smoothly.

-- 
Gleb Smirnoff
Received on Fri Jan 24 2020 - 15:57:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC