[Bug 264179] em(4): 13.1-RELEASE hangs on boot at 82574L (em0, 0x10d3) with I219-V (em1, 0x1a1d ) enabled (Intel Alderlake GbE NIC)
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 18 Sep 2023 00:41:53 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179 --- Comment #17 from Yasuhiro Kimura <yasu@freebsd.org> --- (In reply to Xin LI from comment #16) Yesterday I found newer version of BIOS for the motherboard in question is released. I updated the BIOS of my home server to the latest one and after that onboard NIC is successfully detected as following. yasu@eastasia[1008]% ifconfig -a em0: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=481249b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,WOL_MAGIC,VLAN_HWFILTER,NOMAP> ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect status: no carrier nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> em1: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=481049b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,VLAN_HWFILTER,NOMAP> ether xx:xx:xx:xx:xx:xx inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::xxxx:xxxx:xxxx:xxxx%em1 prefixlen 64 scopeid 0x2 inet6 xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx prefixlen 64 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> yasu@eastasia[1008]% Onboard NIC is detected as em1 and the one inserted to PCIe slot is em0. So the source of the problem seems to be hardware (or firmware). I changed /etc/rc.conf so em1 is used and is watching if em1 works without any problem. I'll keep watching for a while and close this bug report if no problem happens. -- You are receiving this mail because: You are on the CC list for the bug.