Date: Fri, 17 Sep 2021 00:52:48 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258551 Bug ID: 258551 Summary: e1000: "Rework em_msi_link interrupt filter" commit causes to hard lock-up Product: Base System Version: 13.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: firstname.lastname@example.org Created attachment 227954 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227954&action=edit Successful boot sequence https://cgit.freebsd.org/src/commit/sys/dev/e1000?h=stable/13&id=1fb96c59b4ce265ea94eddef5a97c7c075ceaec5 On my Shuttle DS77U Bhyve host, the above mentioned 1fb96c59b4ce265ea94eddef5a97c7c075ceaec5 commit causes the system to freeze during boot. Just backing out the commit solves. The detail is as follows. * Yesterday's 13-STABLE (8895170347fcfd9c9acf413ed408f11b15760b4b) * uname -a FreeBSD fwina.tesla.local 13.0-STABLE FreeBSD 13.0-STABLE #0: Thu Sep 16 18:42:17 JST 2021 email@example.com:/usr/obj/usr/src/amd64.amd64/sys/FWINA amd64 * Part of pciconf -lv: em0@pci0:0:31:6: class=0x020000 rev=0x21 hdr=0x00 vendor=0x8086 device=0x156f subvendor=0x8086 subdevice=0x0000 vendor = 'Intel Corporation' device = 'Ethernet Connection I219-LM' class = network subclass = ethernet igb0@pci0:1:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x1539 subvendor=0x1297 subdevice=0x4052 vendor = 'Intel Corporation' device = 'I211 Gigabit Network Connection' class = network subclass = ethernet * Live LAN connection hooked up only to igb0. em0 has no connection during test. * bridge is fabricated because this host also serves as a traffic filter. autobridge_interfaces="bridge0" autobridge_bridge0="igb0 em0" cloned_interfaces="bridge0" ifconfig_bridge0="up" ifconfig_em0="up" ifconfig_igb0="inet 10.141.30.22 netmask 255.255.255.0 up" * Various modules specified in $devmatch_blacklist so no kld is loaded during test. When the mentioned commit backed out, the system boots without any glitch. When the commit being applied, the system freezes at adding net default: gateway, maybe trying to link up the bridge0 and its member interfaces. The attached ok.jpg shows the successful activation of bridge0 while the ng.jpg is the capture of the hard lock-up. Power-cycle, load the previous kernel and fsck is the only available option to recover. -- You are receiving this mail because: You are the assignee for the bug.