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

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

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

>>> 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

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

>> 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

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

> 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(). >

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

On Fri, Jan 24, 2020 at 04:23:44PM +0900, Masachika ISHIZUKA wrote: M> > 21.01.2020, 20:10, "Nick Hibma" : M> >> That (with the return added, thanks Cy) worked like a charm. M> > Got committed in r357038. M> > Thank you for the report! M> M> Hi. M> M> My machine was panicked on r357061 with

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

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" : H> > That (with the return added, thanks Cy) worked like a charm. H> Got

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

Op vr 24 jan. 2020 om 13:19 schreef Hans Petter Selasky : > Can you try these two patches: > https://reviews.freebsd.org/D23347 > https://reviews.freebsd.org/D23348 These two patches work for me (build- and runtime tested with code from github.com/freebsd/freebsd)

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

On 2020-01-24 09:59, Hans Petter Selasky wrote: On 2020-01-24 09:41, Masachika ISHIZUKA wrote: 21.01.2020, 20:10, "Nick Hibma" : 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

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

On 2020-01-24 09:41, Masachika ISHIZUKA wrote: 21.01.2020, 20:10, "Nick Hibma" : 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

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

>> 21.01.2020, 20:10, "Nick Hibma" : >>> 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

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

> 21.01.2020, 20:10, "Nick Hibma" : >> 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. -- Masachika ISHIZUKA

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

21.01.2020, 20:10, "Nick Hibma" : > That (with the return added, thanks Cy) worked like a charm. Got committed in r357038. Thank you for the report! > > Thanks for the fast response. > > Nick Hibma > n...@van-laarhoven.org > > -- Open Source: We stand on the shoulders of giants. > >>  On 21 Jan

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

That (with the return added, thanks Cy) worked like a charm. Thanks for the fast response. Nick Hibma n...@van-laarhoven.org -- Open Source: We stand on the shoulders of giants. > On 21 Jan 2020, at 18:38, Alexander V. Chernikov wrote: > > 21.01.2020, 17:25, "Nick Hibma" : >> When using a

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

On January 21, 2020 9:38:08 AM PST, "Alexander V. Chernikov" wrote: >21.01.2020, 17:25, "Nick Hibma" : >> When using a trivial program to read from the divert socket and post >back the machine panics instantly when a packet is sent to userland and >back again (incoming packet for the interface,

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

21.01.2020, 17:25, "Nick Hibma" : > When using a trivial program to read from the divert socket and post back the > machine panics instantly when a packet is sent to userland and back again > (incoming packet for the interface, so ifname is set). This is current from > today with no changes > >

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

When using a trivial program to read from the divert socket and post back the machine panics instantly when a packet is sent to userland and back again (incoming packet for the interface, so ifname is set). This is current from today with no changes Any pointers as to how to fix this? Thanks

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

On Tue, Oct 08, 2019 at 05:15:19AM -0700, David Wolfskill wrote: > This was on my laptop (build machine, which was updated in parallel, > but uses a different NIC, had no issues) after a src update from > r353176 to r353298; laptop's NIC is wlan(4) (which is iwn(4), in > this case). After

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

On 10/8/19 4:22 PM, Ryan Stone wrote: I haven't found any good references on the subject, but here's my understanding: - epoch_enter() and epoch_exit() are very inexpensive operations (cheaper than mtx, rw_lock or rm_lock operations) that are use to mark read-only critical sections -

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

I haven't found any good references on the subject, but here's my understanding: - epoch_enter() and epoch_exit() are very inexpensive operations (cheaper than mtx, rw_lock or rm_lock operations) that are use to mark read-only critical sections - epoch_wait() guarantees that no threads that were

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

On Tue, Oct 8, 2019 at 15:01 Julian Elischer wrote: > On 10/8/19 2:42 PM, Walter Parker wrote: > > See the Wikipedia page at https://en.wikipedia.org/wiki/Unix_time > > but I was refering to the new "epoch" faciity in the kernel.. ( man 9 > epoch ) That’s what one would assume given that

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

On 10/8/19 2:42 PM, Walter Parker wrote: See the Wikipedia page at https://en.wikipedia.org/wiki/Unix_time but I was refering to the new "epoch" faciity in the kernel..  ( man 9 epoch  ) https://www.freebsd.org/cgi/man.cgi?query=epoch=0=9=FreeBSD+13-current=default=html Walter On Tue,

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

On 10/8/19 2:45 PM, Matthew Macy wrote: On Tue, Oct 8, 2019 at 14:42 Walter Parker > wrote: See the Wikipedia page at https://en.wikipedia.org/wiki/Unix_time Unrelated. http://concurrencykit.org/slides.html And see also Keir Fraser’s thesis where the idea

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

On Tue, Oct 8, 2019 at 14:42 Walter Parker wrote: > See the Wikipedia page at https://en.wikipedia.org/wiki/Unix_time > > Unrelated. http://concurrencykit.org/slides.html And see also Keir Fraser’s thesis where the idea originated. > > Walter > > On Tue, Oct 8, 2019 at 2:37 PM Julian Elischer

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

See the Wikipedia page at https://en.wikipedia.org/wiki/Unix_time Walter On Tue, Oct 8, 2019 at 2:37 PM Julian Elischer wrote: > Is there a paper or good description of the epoch concept? (more > readable than epoch(9)). > Haven't been to enough BSD confs recently. > > julian >

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

Is there a paper or good description of the epoch concept? (more readable than epoch(9)). Haven't been to enough BSD confs recently. julian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

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

nformation may be found at http://www.catwhisker.org/~david/FreeBSD/head/r353298/ Here's the backtrace (from http://www.catwhisker.org/~david/FreeBSD/head/r353298/core.txt.0): panic: Assertion in_epoch(net_epoch_preempt) failed at /usr/src/sys/net/if.c:3694 cpuid = 3 time = 1570535588 KDB: stack