Re: if_em(4) carrier loss event not recognized with i217; while 82574 does recognize

2019-09-17 Thread Harry Schmalzbauer
Am 11.05.2018 um 19:26 schrieb Harry Schmalzbauer: Bezüglich Harry Schmalzbauer's Nachricht vom 10.05.2018 21:17 (localtime): Hello, if I pull the TP connection from my i217 Clarkville, HEAD still reports media 1000Base-T status "active". Doing the same with the other if_em(4) NIC in that

Re: BBR patches?

2019-09-17 Thread vm finance
correcting a typo: svn co svn://svn.freebsd.org/base/head /usr/src current revision: 352434 Thank you! On Tue, Sep 17, 2019 at 10:11 PM vm finance wrote: > Actually I am on head already as mentioned previously. Pulled it using > yesterday: > > svn co svn://svn.freebsd.org/base/head /use/src >

Re: BBR patches?

2019-09-17 Thread vm finance
Actually I am on head already as mentioned previously. Pulled it using yesterday: >> svn co svn://svn.freebsd.org/base/head /use/src If you could pls let me know the new patch, I can try that. Thanks Sent from my iPhone > On 18-Sep-2019, at 8:56 AM, Randall Stewart wrote: > > There have be

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
There have been several patches pre-this one that provide the infrastructure to support BBR. Release 12.0 will *not* have these patches and will *not* compile it. I have no intention at this point in doing a MFC of this work.. so if you want to run BBR you need to run Head R > On Sep 17, 2019,

Re: BBR patches?

2019-09-17 Thread vm finance
My Kernel config is attached here. Thanks! On Wed, Sep 18, 2019 at 2:26 AM vm finance wrote: > Hi Randall, > > Could you please provide a pointer to the latest patch. I had applied the > one you published Sep-10. > > Following is what I have done: > 1. Picked FreeBSD 12.0 RELEASE VM from osboxes

Re: BBR patches?

2019-09-17 Thread vm finance
Hi Randall, Could you please provide a pointer to the latest patch. I had applied the one you published Sep-10. Following is what I have done: 1. Picked FreeBSD 12.0 RELEASE VM from osboxes.org 2. Got VM up under VMPlayer on x86 laptop 3. Checked out latest codebase from freebsd repo: svn co svn:

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 Kubilay Kocak changed: What|Removed |Added Keywords|needs-qa| Severity|Affects Some P

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #12 from Mark Johnston --- (In reply to Armin Gruner from comment #11) I can't see a problem in that commit, and I haven't been able to find a programmer reference for the jmicron controllers with a quick search. Linux doesn't

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
Looking at your make file log I can’t really tell what you are doing. Its not the BBR or Rack code that is blowing up… Are you cross compiling? I have done the old fashioned kernel make i.e. cd src/sys/amd64/config config headvm cd ../compile/headvm make cleandepend ; make depend; make -j3

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
looking I was at 352408.. let me update and try it R > On Sep 17, 2019, at 1:10 PM, Randall Stewart wrote: > > Hmm > > Did you get the patch I updated too this am? > > I have built it both with and without the bbr stack and had no issue.. there > was > an issue with KTLS before the update t

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
Hmm Did you get the patch I updated too this am? I have built it both with and without the bbr stack and had no issue.. there was an issue with KTLS before the update though. I don’t recognize what you have below there though… R > On Sep 17, 2019, at 11:47 AM, vm finance wrote: > > Got it -

Re: BBR patches?

2019-09-17 Thread vm finance
Got it - thank you! btw, I tried to build the patch but its giving an error. Following is SVN info + make error mesg. Please let me know what am I missing here? Thanks! #svnlite revision Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repositor

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #11 from Armin Gruner --- https://svnweb.freebsd.org/base?view=revision&revision=316820 breaks it -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
Pacing is provided by tcp_hpts.c. The current linux patches do not have to have fq.. they built an alternate means of doing pacing into bbr. In either case our testing has shown that our pacing is more accurate than either fq or the internal pacer :) R > On Sep 17, 2019, at 11:05 AM, vm finance

Re: BBR patches?

2019-09-17 Thread vm finance
Thanks Randall. I was able to apply the patch - now rebuilding the kernel. Would update on how it goes. BTW, is there any description on how lack of tc_fq under FreeBSD is compensated here? The original BBR patches on Linux show that as a must-have? Is that functionality implemented via tcp_rateli

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #10

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #9 from Armin Gruner --- > If you like, I can just revert those changes and test with a newly built > 12-HEAD kernel.. I answer myself: If I revert the changes in if_jme.c introduced between 11.3-RELEASE and 12.0-RELEASE, the

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #8 from Armin Gruner --- BTW I know how to compile kernels; this box can be rebooted anytime, and I am happy to test snapshots (or build from 12-CURRENT, any git branch/tag, I sync with https://github.com/freebsd/freebsd.git Af

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #7 from Armin Gruner --- Created attachment 207577 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207577&action=edit pciconf -l output -- You are receiving this mail because: You are the assignee for the bug. You ar

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #6 from Armin Gruner --- Created attachment 207576 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207576&action=edit dmesg.boot -- You are receiving this mail because: You are on the CC list for the bug. You are the

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #5 from Armin Gruner --- Sure: root@eeetop:~ # uname -a FreeBSD eeetop 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC amd64 Output of dmesg after boot and pciconf is attached; if I remove the disables from loader.conf, pci

Re: BBR patches?

2019-09-17 Thread Randall Stewart via freebsd-net
You should be able to compile it against the current head. I re-doing that now (had an issue with my machine and had to roll it back to a backup). When I put the patch up on Sept 10th it complied with and without BBR on whatever was that rev.. Looking in the commit logs that would have been aro

Re: BBR patches?

2019-09-17 Thread vm finance
Hi Randall, Thanks for releasing BBR patch: https://reviews.freebsd.org/D21582#change-xcAWBif3E9Jq Could you please let me know what SVN/GIT label tag this is based on? I would like to patch and experiment with it. I couldn't find this info in the released patch. Thanks a lot! On Tue, Sep 10, 2