[Bug 264179] 13.1-RELEASE hands in boot with Intel Alderlake GbE NIC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179 --- Comment #2 from Yasuhiro Kimura --- (In reply to Kubilay Kocak from comment #1) > - Can you confirm boot behaviour is OK on 12.1-RELEASE ? Do you mean 12.3-RELEASE? If so, same hangup happens with it. > - Is the system able to boot single user? (to obtain and attach pciconf -lv > and usbconfig list output) No. Hangup happens before reaching single user shell. But on 13.0-RELEASE `pciconf -lv` gets following result. yasu@maybe[1002]% pciconf -lv ~ hostb0@pci0:0:0:0: class=0x06 rev=0x05 hdr=0x00 vendor=0x8086 device=0x4630 subvendor=0x1458 subdevice=0x5000 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 rev=0x05 hdr=0x01 vendor=0x8086 device=0x460d subvendor=0x1458 subdevice=0x5000 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI vgapci0@pci0:0:2:0: class=0x03 rev=0x0c hdr=0x00 vendor=0x8086 device=0x4692 subvendor=0x1458 subdevice=0xd000 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:10:0: class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x467d subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7ae0 subvendor=0x1458 subdevice=0x5007 vendor = 'Intel Corporation' class = serial bus subclass = USB none1@pci0:0:20:2: class=0x05 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7aa7 subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = memory subclass = RAM none2@pci0:0:21:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7acc subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none3@pci0:0:21:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7acd subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none4@pci0:0:21:2: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7ace subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none5@pci0:0:21:3: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7acf subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none6@pci0:0:22:0: class=0x078000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7ae8 subvendor=0x1458 subdevice=0x1c3a vendor = 'Intel Corporation' class = simple comms ahci0@pci0:0:23:0: class=0x010601 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7ae2 subvendor=0x1458 subdevice=0xb005 vendor = 'Intel Corporation' class = mass storage subclass = SATA none7@pci0:0:25:0: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7afc subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none8@pci0:0:25:1: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7afd subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus pcib2@pci0:0:28:0: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7ab8 subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:4: class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7abc subvendor=0x1458 subdevice=0x5001 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a87 subvendor=0x1458 subdevice=0x5001 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA hdac0@pci0:0:31:3: class=0x040300 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7ad0 subvendor=0x1458 subdevice=0xa194 vendor = 'Intel Corporation' class = multimedia subclass = HDA none9@pci0:0:31:4: class=0x0c0500 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7aa3 subvendor=0x1458 subdevice=0x5001 vendor = 'Intel Corporation' class = serial bus subclass = SMBus none10@pci0:0:31:5: class=0x0c8000 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7aa4 subvendor=0x subdevice=0x vendor = 'Intel Corporation' class = serial bus none11@pci0:0:31:6: class=0x02 rev=0x11 hdr=0x00 vendor=0x8086 device=0x1a1d subvendor=0x1458 subdevice=0xe000 vendor = 'Intel Corporation' device = 'Ethernet Connection (17) I219-V' class = network subclass = ethernet em0@pci0:1:0:0: class=0x02 rev=0x00 hdr=0x00 vendor=0x8086 device=0x10d3 subvendor=0x8086 subdevice=0xa01f vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network
[Bug 264179] 13.1-RELEASE hands in boot with Intel Alderlake GbE NIC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179 --- Comment #3 from Yasuhiro Kimura --- According to the suggestion in freebsd-stable ML, I added 'hint.em.1.disabled=1' to /boot/loader.conf and then 13.1-RELEASE boots successfully. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Re: FreeBSD 12.3-p5: problems vnet on if_bridge
Tue, 24 May 2022 17:17:19 +0200 - FreeBSD User : > > could you solve the problem? I think I ran into the same problem. > > I opened a Ticket. > > I couldn't solve the problem. > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264198 > > > > I seems to be related to IPFW and effects vnet-Jails and also bhyve > > VMs. > > There is also a PR regarding vnet/if_bridge/routing issues, at > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240106 > > but I can not guarantee this PR is in any way similaror adjacent to > the problem of mine (and probably yours). Difficult to say if the problems are related. In my problem IPFW plays a role. Are you using IPFW? If so, please take a look at the issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264198 I described very simple setup to reproduce the bug, in a Bhyve VM with only one Interface: vtnet0---bridge0---epaira0---epairb0 vm # ifconfig bridge create mtu 1400 vm # ifconfig epair create mtu 1400 vm # ifconfig bridge0 addm epair0a vm # ifconfig bridge0 addm vtnet0 vm # ifconfig epair0a up vm # ifconfig epair0b inet /28 mtu 1400 up vm # ifconfig bridge0 up vm # nc -v -l > /dev/null the only IPFW rule is vm # ipfw list 65535 allow ip from any to any from another host (in the same network) I send data with nc: dd if=/dev/zero bs=1024k count=6 | nc -v result: 6291456 bytes transferred in 70.693446 secs (88996 bytes/sec) after 'service ipfw stop' on vm-a, it is about 700 times faster )-: 6291456 bytes transferred in 0.100673 secs (62493675 bytes/sec) I wonder if IPFW + bridge is broken in 12.3. ... pgp1bwW79khHW.pgp Description: Digitale Signatur von OpenPGP
[Bug 263756] igb interface not receiving vlan packets since 12.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756 Ryan Steinmetz changed: What|Removed |Added CC||z...@freebsd.org --- Comment #4 from Ryan Steinmetz --- I ran into this as well. This resolved my issue: ifconfig igb0 -vlanhwfilter -vlanhwtag -- You are receiving this mail because: You are the assignee for the bug.
[Bug 263756] igb interface not receiving vlan packets since 12.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756 --- Comment #5 from Natalino Picone --- (In reply to Ryan Steinmetz from comment #4) This is not working as the 12.3 intel driver contains a bug. ifconfig reports that features have been disabled, but they are not. See https://reviews.freebsd.org/D33154 which I think should also be merged on 12.3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 263756] igb interface not receiving vlan packets since 12.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756 --- Comment #6 from Ryan Steinmetz --- (In reply to Natalino Picone from comment #5) My use case is closer to what s...@42.org described--where I have vlan interfaces created. I don't think my situation is identical to what you reported, but, seems related. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 264248] ib_cm: Fix a resource leak in ib_cm_insert_listen()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264248 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.