Date: Fri, 10 Feb 2023 12:23:18 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 268490] [igb] [lagg] [vlan]: Intel i210 performance severely degraded Message-ID: <bug-268490-7501-5l8ShOdHW1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268490-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-268490-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268490 --- Comment #5 from Kevin Bowling <kbowling@freebsd.org> --- (In reply to Daniel Duerr from comment #4) 1) Clone FreeBSD src, check out 12.4: pkg install git-lite git clone https://git.freebsd.org/src.git /usr/src cd /usr/src git checkout releng/12.4 2) Start the bisecting using the 12.4 release branch as a known bad point, = 12.2 as known good and limit the search to the e1000 driver commits: cd /usr/src git bisect start releng/12.4 releng/12.2 -- sys/dev/e1000 3) Build and install the kernel: cd /usr/src make -j `sysctl -n hw.ncpu` buildkernel KERNCONF=3DGENERIC-NODEBUG make installkernel KERNCONF=3DGENERIC-NODEBUG 4) Reboot the system. You will be in the new kernel (confirm with uname -a= , it will show you the build date and git hash). 5) Perform some test like your iperf. 6) If the performance is good: cd /usr/src git bisect good Repeat step 3 & 4 7) If the performance is bad: cd /usr/src git bisect bad Repeat step 3 & 4 8) Keep repeating steps 3 through 7. After a handful of repetitions, you w= ill run out of commits to test and it will spit out the first bad hash. Post t= hat here. 9) To restore your system to a desired kernel, say 12.4 with security patch= es: git checkout releng/12.2 Repeat step 3 & 4 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268490-7501-5l8ShOdHW1>