Date: Tue, 26 Nov 2019 05:07:54 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 166724] [re] if_re watchdog timeout Message-ID: <bug-166724-7501-gxOcbqdPx9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-166724-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-166724-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166724 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #39 from Chris Hutchinson <portmaster@bsdforge.com> --- I'd also like to add a "me too" here. I've been evaluating how well FreeBSD works with dual port NICs with the intent of using multiport 10G (Mellanox?) cards if it performs well. Years of experience with re(4)'s has shown that they are stable performers, and inexpensive. Which is why I chose it for the trial. It worked well for some 4-6 mos. But we're now plagued with watchdog timeout errors, with the *only* working solution being; to bounce the box(es). I'm *guessing* greater pressure on the wire(s) to be the reason for it happening now, and not earlier. Any insight (with a cure) would be *greatly* appreciated. Details follow: 11.1-STABLE r327867 amd64 watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout watchdog timeout rc.conf(5) ifconfig_re0=3D"inet AA.BBB.CC.XX netmask 255.255.255.0 rxcsum txcsum tso4" ifconfig_re1=3D"inet AA.BBB.CC.WW netmask 255.255.255.0 rxcsum txcsum tso4" ifconfig_re1_alias0=3D"inet AA.BBB.CC.ZZ netmask 255.255.255.0" ifconfig(8) re0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3D8219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_= MAGIC,LINKSTATE> ether 00:13:3b:0f:13:44 hwaddr 00:13:3b:0f:13:44 inet6 fe80::213:3bff:fe0f:1344%re0 prefixlen 64 scopeid 0x1=20 inet AA.BBB.CC.XX netmask 0xffffff00 broadcast 24.113.41.255=20 nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active re1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3D8219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_= MAGIC,LINKSTATE> ether 00:13:3b:0f:13:45 hwaddr 00:13:3b:0f:13:45 inet AA.BBB.CC.WW netmask 0xffffff00 broadcast 24.113.41.255=20 inet AA.BBB.CC.ZZ netmask 0xffffff00 broadcast 24.113.41.255=20 inet6 fe80::213:3bff:fe0f:1345%re1 prefixlen 64 scopeid 0x2=20 nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=3D600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128=20 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3=20 inet 127.0.0.1 netmask 0xff000000=20 nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL> groups: lo=20 pciconf(8) re0@pci0:5:0:0: class=3D0x020000 card=3D0x012310ec chip=3D0x816810ec rev=3D= 0x07 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll= er' class =3D network subclass =3D ethernet re1@pci0:6:0:0: class=3D0x020000 card=3D0x012310ec chip=3D0x816810ec rev=3D= 0x07 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll= er' class =3D network subclass =3D ethernet Thanks again! --Chris --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-166724-7501-gxOcbqdPx9>