Date: Mon, 2 Aug 2021 10:51:46 -0700 From: Kevin Bowling <kevin.bowling@kev009.com> To: FreeBSD Net <freebsd-net@freebsd.org> Cc: Franco Fichtner <franco@lastsummer.de> Subject: igb(4) and VLAN issue? Message-ID: <CAK7dMtCJhKVo8agr_VGbtGHZeKK8_8ip%2B6bY_yaW45wo42caZQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, I caught wind that an igb(4) commit I've done to main and that has been in stable/12 for a few months seems to be causing a regression on opnsense. The commit in question is https://cgit.freebsd.org/src/commit/?id=eea55de7b10808b86277d7fdbed2d05d3c6db1b2 The report is at: https://forum.opnsense.org/index.php?topic=23867.0 I haven't heard of this issue elsewhere and cannot replicate it on my I210s running main. I've gone over the code changes line by line several times and verified all the logic and register writes and it all looks correct to my understanding. The only hypothesis I have at the moment is it may be some subtle timing issue since VLAN changes unnecessarily restart the interface on e1000 until I push in a work in progress to stop doing that. I'd like to see the output of all the processes or at least the process configuring the VLANs to see where it is stuck. Franco, do you have the ability to 'control+t' there or otherwise set up a break into a debugger? Stacktraces would be a great start but a core and a kernel may be necessary if it isn't obvious. Regards, Kevin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK7dMtCJhKVo8agr_VGbtGHZeKK8_8ip%2B6bY_yaW45wo42caZQ>