Date: Tue, 16 Mar 2021 18:29:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours Message-ID: <bug-254341-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254341 Bug ID: 254341 Summary: igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours Product: Base System Version: 12.2-RELEASE Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: vlad.shabanov@gmail.com Created attachment 223330 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D223330&action= =3Dedit full dmesg.boot I have problem with FreeBSD 12.2p1 The problem started on FreeBSD 12.0 and persists till now. The network hung just after the boot. Ifconfig down+up solves the problem f= or next 5-20 hours. I don=E2=80=99t know how to force NIC to hung immediately.= Just do ifconfig up/down and wait for next N hours. MBoard: SuperMicro X10SRI-F NIC: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xe020-0xe03f mem 0xfb120000-0xfb13ffff,0xfb144000-0xfb147fff irq 43 at device 0.0 on pci5 firewall: pf=20 There is no vlan, only jails working on 10.0.0.1/16 Now I use simple watchdog script staring every minute. The script pings the gateway and do ifconfig down/up on error. The script dumps these values every minute: /sbin/pfctl -si > /root/WATCHDOG/failure.txt /usr/bin/netstat -m >> /root/WATCHDOG/failure.txt /sbin/sysctl -a | /usr/bin/grep dev.igb >> /root/WATCHDOG/failure.t= xt I have two files: one before the hung, the second one just after the hung. = Hope that some values inside can help. =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2= =80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80= =94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94= =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 - from dmesg.boot igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xe020-0xe03f mem 0xfb120000-0xfb13ffff,0xfb144000-0xfb147fff=20 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: Using an MSI interrupt igb0: Ethernet address: ac:1f:6b:02:8a:c4 igb0: netmap queues/slots: TX 1/1024, RX 1/1024 =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2= =80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80= =94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94= =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 $ ifconfig igb0 igb0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De507bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSU= M,TSO4,TSO6,LRO,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether ac:1f:6b:02:8a:c4 inet IP-ADDR netmask 0xffffff00 broadcast IP-ADDR media: Ethernet 100baseTX <full-duplex> status: active nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2= =80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80= =94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94= =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94 - /etc/rc.conf: - zfs_enable=3D"YES" sshd_enable=3D"YES" ntpd_enable=3D"YES" powerd_enable=3D"YES" local_unbound_enable=3D"YES" hostname=3D"..." ifconfig_igb0=3D"inet IP-ADDR netmask 255.255.255.0" defaultrouter=3D"IP-ADDR" ifconfig_lo0_alias0=3D"inet 10.0.0.1 netmask 0xffff0000" pf_enable=3D"YES" pflog_enable=3D"YES" --=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-254341-227>