Re: somewhat reproducable vimage panic

On 2020-07-23 21:26, Bjoern A. Zeeb wrote: That’ll probably work;  still, the deferred teardown work seems wrong to me;  I haven’t investigated;  the patch kind-of says exactly that as well: if “wait until deferred stuff is done” is all we are doing, why can we not do it on the spot then? Hi

Re: somewhat reproducable vimage panic

On 2020-07-25 21:21, John-Mark Gurney wrote: So far so good... I am getting these on occasion: in6_purgeaddr: err=65, destination address delete failed Maybe you could add a "kdb_backtrace()" call when that error happens? --HPS ___

Re: somewhat reproducable vimage panic

On 2020-07-25 21:21, John-Mark Gurney wrote: Yeah, agreed. I think hselasky has a better fix: https://reviews.freebsd.org/D24914 I just saw his e-mail in a different thread. I'm testing out this patch now, and let people know how it goes.. It'll be nice to not have to worry about these

Re: somewhat reproducable vimage panic

John-Mark Gurney wrote this message on Thu, Jul 23, 2020 at 16:49 -0700: > Kristof Provost wrote this message on Thu, Jul 23, 2020 at 11:02 +0200: > > On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote: > > > On 23 Jul 2020, at 8:09, Kristof Provost wrote: > > > > > >> On 23 Jul 2020, at 9:19, Kristof

Re: somewhat reproducable vimage panic

Kristof Provost wrote this message on Thu, Jul 23, 2020 at 11:02 +0200: > On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote: > > On 23 Jul 2020, at 8:09, Kristof Provost wrote: > > > >> On 23 Jul 2020, at 9:19, Kristof Provost wrote: > >>> On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: > So,

Re: somewhat reproducable vimage panic

On 23 Jul 2020, at 9:02, Kristof Provost wrote: On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote: On 23 Jul 2020, at 8:09, Kristof Provost wrote: On 23 Jul 2020, at 9:19, Kristof Provost wrote: On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: So, it's pretty easy to trigger, just attach a

Re: somewhat reproducable vimage panic

On Thu, 23 Jul 2020 11:02:01 +0200 "Kristof Provost" wrote: > Yeah, agreed. I think hselasky has a better fix: > https://reviews.freebsd.org/D24914 Yup, that should be it. > > I just saw his e-mail in a different thread. > > Best regards, > Kristof >

Re: somewhat reproducable vimage panic

On 23 Jul 2020, at 11:00, Bjoern A. Zeeb wrote: On 23 Jul 2020, at 8:09, Kristof Provost wrote: On 23 Jul 2020, at 9:19, Kristof Provost wrote: On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: So, it's pretty easy to trigger, just attach a couple USB ethernet adapters, in my case, they were

Re: somewhat reproducable vimage panic

On 23 Jul 2020, at 8:09, Kristof Provost wrote: On 23 Jul 2020, at 9:19, Kristof Provost wrote: On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: So, it's pretty easy to trigger, just attach a couple USB ethernet adapters, in my case, they were ure, but likely any two spare ethernet

Re: somewhat reproducable vimage panic

On 23 Jul 2020, at 9:19, Kristof Provost wrote: On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: So, it's pretty easy to trigger, just attach a couple USB ethernet adapters, in my case, they were ure, but likely any two spare ethernet interfaces will work, and wire them back to back.. I’ve

Re: somewhat reproducable vimage panic

On 23 Jul 2020, at 0:15, John-Mark Gurney wrote: > So, it's pretty easy to trigger, just attach a couple USB ethernet > adapters, in my case, they were ure, but likely any two spare ethernet > interfaces will work, and wire them back to back.. > I’ve been able to trigger it using epair as well:

Re: somewhat reproducable vimage panic

Bjoern A. Zeeb wrote this message on Wed, Jul 22, 2020 at 20:43 +: > On 22 Jul 2020, at 19:34, John-Mark Gurney wrote: > > > John-Mark Gurney wrote this message on Tue, Jul 21, 2020 at 23:05 > > -0700: > >> Peter Libassi wrote this message on Wed, Jul 22, 2020 at 06:54 +0200: > >>> Is this

Re: somewhat reproducable vimage panic

On 22 Jul 2020, at 19:34, John-Mark Gurney wrote: John-Mark Gurney wrote this message on Tue, Jul 21, 2020 at 23:05 -0700: Peter Libassi wrote this message on Wed, Jul 22, 2020 at 06:54 +0200: Is this related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985

Re: somewhat reproducable vimage panic

John-Mark Gurney wrote this message on Tue, Jul 21, 2020 at 23:05 -0700: > Peter Libassi wrote this message on Wed, Jul 22, 2020 at 06:54 +0200: > > Is this related to > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985 > >

Re: somewhat reproducable vimage panic

Peter Libassi wrote this message on Wed, Jul 22, 2020 at 06:54 +0200: > Is this related to > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985 > and > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 >

Re: somewhat reproducable vimage panic

Is this related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985 and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238326 /Peter > 21 juli 2020 kl. 22:23

Re: somewhat reproducable vimage panic

Marko Zec wrote this message on Tue, Jul 21, 2020 at 11:31 +0200: > On Tue, 21 Jul 2020 02:16:55 -0700 > John-Mark Gurney wrote: > > > I'm running: > > FreeBSD test 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r362596: Thu Jun 25 > > 05:02:51 UTC 2020 > >

Re: somewhat reproducable vimage panic

On Tue, 21 Jul 2020 02:16:55 -0700 John-Mark Gurney wrote: > I'm running: > FreeBSD test 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r362596: Thu Jun 25 > 05:02:51 UTC 2020 > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 > > and I'm working on improve the if_ure

somewhat reproducable vimage panic

I'm running: FreeBSD test 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r362596: Thu Jun 25 05:02:51 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and I'm working on improve the if_ure driver. I've put together a little script that I've attached that I'm