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

From: Masachika ISHIZUKA <ish_at_amail.plala.or.jp>
Date: Sat, 25 Jan 2020 14:22:22 +0900 (JST)
>>>> 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

  r357102 without D23347 and D23348 works fine.
  Thank you very much.
-- 
Masachika ISHIZUKA
Received on Sat Jan 25 2020 - 04:22:36 UTC

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