Re: Traffic "corruption" in 12-stable
On Mon, Aug 03, 2020 at 05:22:37PM -0400, Joe Clarke wrote: > > On Jul 27, 2020, at 15:41, Joe Clarke wrote: > >> On Jul 27, 2020, at 15:01, Mark Johnston wrote: > >> There are some fixes for vmx not present in stable/12 (yet). I did a > >> merge of a number of outstanding revisions. Would you be able to test > >> the patch? I haven't observed any problems with it on a host using igb, > >> but I have no ability to test vmx at the moment. > > > > I’m down to test anything. I did notice quite a few vmxnet3 changes around > > performance that appealed to me. I tried a few of them on my last kernel. > > That took much longer to exhibit the problem, but eventually did. > > > > I can tell you I don’t have all of these patches in, though. I’ll build > > with this diff and start running it now. I’ll let you know how it goes. > > So it’s been just over a week of runtime with this full patch set. I have > seen no further issues with ingress packet “truncation”, and performance has > been what I expect. I’m going to keep running, but I think this seems like a > good set to MFC. Done in r363844, thanks. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Traffic "corruption" in 12-stable
> On Aug 4, 2020, at 11:51, Mark Johnston wrote: > > On Mon, Aug 03, 2020 at 05:22:37PM -0400, Joe Clarke wrote: >>> On Jul 27, 2020, at 15:41, Joe Clarke wrote: On Jul 27, 2020, at 15:01, Mark Johnston wrote: There are some fixes for vmx not present in stable/12 (yet). I did a merge of a number of outstanding revisions. Would you be able to test the patch? I haven't observed any problems with it on a host using igb, but I have no ability to test vmx at the moment. >>> >>> I’m down to test anything. I did notice quite a few vmxnet3 changes around >>> performance that appealed to me. I tried a few of them on my last kernel. >>> That took much longer to exhibit the problem, but eventually did. >>> >>> I can tell you I don’t have all of these patches in, though. I’ll build >>> with this diff and start running it now. I’ll let you know how it goes. >> >> So it’s been just over a week of runtime with this full patch set. I have >> seen no further issues with ingress packet “truncation”, and performance has >> been what I expect. I’m going to keep running, but I think this seems like >> a good set to MFC. > > Done in r363844, thanks. Thank you. On day 8, and still no issues. Joe --- PGP Key : http://www.marcuscom.com/pgp.asc ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Bug 237666 - repeated messages of "uhub_reattach_port: giving up port reset - device vanished"
I was told to resubmit this with the bug's title in the subject line. Therefore, I am. I am just inquiring to see if any progress had been made regarding bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 This bug affects both the 12.x and 13.x branches of FreeBSD. Fortunately, it does not affect <= 11.x branches. FreeBSD 12.2 is due out in October and version 13.0 only five months later. At present, this bug infects both the 12.x and 13.x branches making updating systems beyond 11.x impossible for users of the afflicted systems. The fact that this bug has gone unremedied for so long is somewhat disheartening. -- Gerard pgp1Y_xXdFNiv.pgp Description: OpenPGP digital signature
