Any gigabit hardware downstream causes – em0: Watchdog timeoout -- resetting
-
I'm running 2.1-BETA1 (i386)
Anytime I connect a Gigabit switch or hub to any interface; em0 (my wan interface) fails. Eventually the following message shows up on the console:
em0: Watchdog timeoout – resetting
em0: Hardware Initialization Failed
em0: Unable to initialize the hardwareTo be clear:
I have 3 interfaces --
em0
em1
em2They're all Intel 8390MT Pro/1000MT Gigabit PCI Ethernet Network PCI Adapter Cards
Only em0 (wan) and em1 (lan) are configured. When I connect any Gigabit hardware to any of the interfaces, I get the error. I've tried Netgear gigabit hubs, a Mikrotik RouterBoard RB250G RB250GS Smart Gigabit Switch and a D-link 24 port gigabit switch.
Whenever a gigabit device is connected to any of the interfaces.... em0 fails. I had the same problem with realtek 8110 based NICs.
For now I can only run my pfSense device at 100Mbps, this isn't acceptable long term. I'll need to find a solution or switch off pfSense-- which I don't want to do because of all the other benefits!
Any ideas? Advice? Help is greatly appreciated.
Here's a chunk of dmesg while it's working:
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2790.72-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9
Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x4400 <cnxt-id,xtpr>real memory = 1610612736 (1536 MB)
avail memory = 1553387520 (1481 MB)
ACPI APIC Table: <dell 2400 ="">ioapic0: Changing APIC ID to 1
ioapic0 <version 2.0="">irqs 0-23 on motherboard
wlan: mac acl policy registered
kbd1 at kbdmux0
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
acpi0: <dell 2400 ="">on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, f00000 (3) failed
acpi0: reservation of 1000000, 5ee74000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <acpi cpu="">on acpi0
acpi_button0: <power button="">on acpi0
pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus="">on pcib0
vgapci0: <vga-compatible display="">mem 0xe8000000-0xefffffff,0xfeb80000-0xfebfffff irq 16 at device 2.0 on pci0
agp0: <intel 82845m="" (845m="" gmch)="" svga="" controller="">on vgapci0
agp0: aperture size is 128M, detected 892k stolen memory
uhci0: <intel 82801db="" (ich4)="" usb="" controller="" usb-a="">port 0xff80-0xff9f irq 16 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <intel 82801db="" (ich4)="" usb="" controller="" usb-a="">on uhci0
uhci1: <intel 82801db="" (ich4)="" usb="" controller="" usb-b="">port 0xff60-0xff7f irq 19 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <intel 82801db="" (ich4)="" usb="" controller="" usb-b="">on uhci1
uhci2: <intel 82801db="" (ich4)="" usb="" controller="" usb-c="">port 0xff40-0xff5f irq 18 at device 29.2 on pci0
uhci2: [ITHREAD]
usbus2: <intel 82801db="" (ich4)="" usb="" controller="" usb-c="">on uhci2
ehci0: <intel 82801db="" l="" m="" (ich4)="" usb="" 2.0="" controller="">mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus3: EHCI version 1.0
usbus3: <intel 82801db="" l="" m="" (ich4)="" usb="" 2.0="" controller="">on ehci0
pcib1: <acpi pci-pci="" bridge="">at device 30.0 on pci0
pci1: <acpi pci="" bus="">on pcib1
em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xdec0-0xdeff mem 0xfe940000-0xfe95ffff,0xfe960000-0xfe97ffff irq 16 at device 4.0 on pci1
em0: [FILTER]
em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xdf00-0xdf3f mem 0xfe980000-0xfe99ffff,0xfe9a0000-0xfe9bffff irq 17 at device 5.0 on pci1
em1: [FILTER]
em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xdf40-0xdf7f mem 0xfe9c0000-0xfe9dffff,0xfe9e0000-0xfe9fffff irq 18 at device 6.0 on pci1
em2: [FILTER]
bfe0: <broadcom bcm4401="" fast="" ethernet="">mem 0xfe93e000-0xfe93ffff irq 17 at device 9.0 on pci1
miibus0: <mii bus="">on bfe0
bmtphy0: <bcm4401 10="" 100basetx="" phy="">PHY 1 on miibus0
bmtphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bfe0: [ITHREAD]
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <intel ich4="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7ffff irq 18 at device 31.1 on pci0
ata0: <ata channel="">at channel 0 on atapci0
ata0: [ITHREAD]
ata1: <ata channel="">at channel 1 on atapci0
ata1: [ITHREAD]
pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
atrtc0: <at realtime="" clock="">port 0x70-0x7f irq 8 on acpi0
fdc0: <floppy drive="" controller="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
atkbd0: <at keyboard="">irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
ppc0: <parallel port="">port 0x378-0x37f,0x778-0x77f irq 7 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppc0: [ITHREAD]
ppbus0: <parallel port="" bus="">on ppc0
plip0: <plip network="" interface="">on ppbus0
plip0: [ITHREAD]
lpt0: <printer>on ppbus0
lpt0: [ITHREAD]
lpt0: Interrupt-driven port
ppi0: <parallel i="" o="">on ppbus0
pmtimer0 on isa0
orm0: <isa option="" roms="">at iomem 0xc0000-0xcb7ff,0xcb800-0xcc7ff,0xcc800-0xcd7ff,0xcd800-0xce7ff,0xce800-0xcffff pnpid ORM0000 on isa0
sc0: <system console="">at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
Timecounter "TSC" frequency 2790721552 Hz quality 800
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 480Mbps High Speed USB v2.0
ugen0.1: <intel>at usbus0
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <intel>at usbus1
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
ugen2.1: <intel>at usbus2
uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
ugen3.1: <intel>at usbus3
uhub3: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus3
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
ad0: 8063MB <wdc wd84aa="" 29.05t29="">at ata0-master UDMA66
acd0: CDRW <hl-dt-st gce-8483b="" b105="">at ata0-slave UDMA33
uhub3: 6 ports with 6 removable, self powered
Trying to mount root from ufs:/dev/ad0s1a
em0: link state changed to UP</hl-dt-st></wdc></intel></intel></intel></intel></intel></intel></intel></intel></cpu></generic></system></isa></parallel></printer></plip></parallel></parallel></at></keyboard></floppy></at></serial></ata></ata></intel></isa></pci-isa></bcm4401></mii></broadcom></intel(r)></intel(r)></intel(r)></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></vga-compatible></acpi></acpi></power></acpi></dell></software></version></dell ></cnxt-id,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe> -
This might not be particularly relevant to the problem you have reported but your I/O capacity is way over-committed. All your NICs are on the same PCI bus. If that is a standard PCI bus then you will be hard pressed to get 1Gbps (b = BITS) through it. Your NICs could want 3*2Gbps + 200Mbps + PCI bus overheads.
I suggest you try connecting at most one Gigabit capable device and force everything else to run at 100Mbps, or even better, force everything to run at 100Mbps or less.
If your WAN speed to the Internet is 100Mbps or less there is nothing to be gained by running the link to your modem at 1Gbps.
-
That is a strange problem. You connect things to a downstream interface and the upstream NIC fails. :-\
One thing I would try here is disabling any hardware you don't need in the bios. I'd start with the floppy controller and parallel port but also try USB controllers, if you're not using them and is the Broadcom NIC on board?
You have a number of things using irq16 including em0, not necessarily a problem.
Steve
-
Hello!
Thanks for the replies!! Currently I have a net gear 10/100 hub connected to the lan side (em1) and then to a netgear 10/100/1000 hub with my Wireless router and other machines connected to it. This is the only way I can connect the 10/100/1000 hardware to the router.
I definitely understand about the PCI bus limits and the upstream speed being the limiting factor on Internet bound traffic and I appreciate the reminder– to that end I disabled everything possible in BIOS including the on-board NIC and removed one of the PCI cards with no luck.
So, there are two reasons why I need to get this figured out.
- We sometimes have high internal traffic and multiple end points making large transfers so the Gigabit switches make a big difference in that case. To be sure the router speed wasn't involved in this I did the following test
---- run iperf between two nodes on the gigabit hub
---- move the cables to the 10/100 hubBoth tests were with the 10/100 in between the gigabit hub and the router, here's the results:
Server listening on TCP port 5001
TCP window size: 8.00 KByte (default)[180] local 192.168.1.107 port 5001 connected with 192.168.1.112 port 1625
[ ID] Interval Transfer Bandwidth
[180] 0.0-10.1 sec 666 MBytes 552 Mbits/sec
[196] local 192.168.1.107 port 5001 connected with 192.168.1.112 port 1638
[196] 0.0-10.0 sec 51.5 MBytes 43.0 Mbits/secIt's 10+ times faster between local end-points!
- I want to be able to use Gigabit hardware in the Lan, I can isolate the lan NIC in the PFSense box for now with a 10/100 hub, but it's not a scalable solution as I'm testing this for potential build outs for small business networks.
Considering the fact that I may just have some funky hardware, I'm not adverse to building a different machine, but I don't want to hit a similar problem. I'm hoping to understand what's causing it before investing in more test hardware.
I've been able to run linux / iptables routers on this same hardware with the same gigabit hardware downstream with no troubles.
Thanks again for any insight you can provide! I love PFSense and hope to get this worked out so I can use it on a larger scale!!!
Is there a Golden hardware list somewhere that I haven't stumbled upon yet?
Thanks,
-j. -
It's 10+ times faster between local end-points!
"local" (same subnet) traffic will normally bypass the router.
- I want to be able to use Gigabit hardware in the Lan, I can isolate the lan NIC in the PFSense box for now with a 10/100 hub, but it's not a scalable solution as I'm testing this for potential build outs for small business networks.
1. I'm guessing you won't be using Pentium 4 equipment in the "build outs for small business networks". Any "modern" PC based system is likely to provide considerably higher I/O bandwidth than a single PCI bus.
2. You haven't given much detail of what you want the equipment doing for small business networks. If it is for basis firewalling an ALIX could well be suitable for internet speeds up to about 85MBps. Because "local" systems would normally communicate directly through a switch (bypassing the router) there might not be a need for the router/firewall to run interfaces at Gigabit speeds.
I've been able to run linux / iptables routers on this same hardware with the same gigabit hardware downstream with no troubles.
Maybe the Linux configuration enables flow control on the NICs and pfSense doesn't. I'll need to look for another thread about flow control. I'll update this reply when I find that thread.
Is there a Golden hardware list somewhere that I haven't stumbled upon?
Such a list can't tell you whether a particular configuration will be suitable for your particular application. How would you characterise the requirements you are attempting to address? In particular, where do you need gigabit speeds and why?
Edit: The thread I mentioned is at http://forum.pfsense.org/index.php/topic,57037.0.html though it takes a few replies to get into the relevant section.
-
Whilst I completely agree with everything Wallabybob said above there is no reason why your hardware shouldn't be working as you have it, or no obvious reason at least.
Considering the fact that I may just have some funky hardware, I'm not adverse to building a different machine, but I don't want to hit a similar problem. I'm hoping to understand what's causing it before investing in more test hardware.
I think this is probably it. You have some combination of hardware that is conflicting somehow and causing you box to run out of some resource. It still seems very odd that em0 goes down but that isn't the interface being connected to the GigE hardware. :-\ Since you have spare NICs I would try leaving em0 unassigned and using the others instead. As Wallabybob said your WAN connection may not be >100Mbps (you haven't said yet) so you could use the Broadcom NIC for that.
My home pfSense box is P4 based with 10 interfaces including 3 Intel 'em' GigE NICs and I've never seen anything like this.Steve
-
My home pfSense box is P4 based with 10 interfaces including 3 Intel 'em' GigE NICs and I've never seen anything like this.
Different chipset? You don't drive your NICs so hard? Or maybe whatever you have connected to them doesn't drive them so hard?
-
I think it's very likely a different chipset. The X-Peak has the server specific 875P/6300ESB which I'm sure helps. However my own box has an underclocked CPU and I have run tests through it as fast I could push. It's never even blinked even if it's not that quick. I say this just as an example that it's not inherently a P4 is too slow problem. This is something that shouldn't be happening.
Steve
-
Hi all –
First, thanks again for all the help~ Here's the latest...
I moved different NICs to different PCI slots, and ran with only two: any combination will cause a watchdog timeout when a GbE device is connected. Using the on-board 10/100 Broadcom NIC I can connect GbE devices to any of the em* interfaces without getting the watchdog timeout, so it does look like something is getting resource constrained on the PCI bus.
While my upstream internet connection is only about 20Mbps down I do have a GbE lan connection on the modem. I sometimes place a hub/switch there also to mirror traffic. Strange that the GbE LAN port on the modem did not trigger the watchdog timeout but a GbE hub did when connect between WAN and modem.
Again, it's not important to have Gigabit speeds, it's just the hardware that I have and that is most available, it's problematic to have to use a 10/100 hub to avoid hard failures.
The GbE hub does work in line with the broadcom where it failed on the Intel PCI controller.
For this box at home, I'm going to call it solved unless anyone wants me to experiment to see if we can find the root cause. Again, a straight Linux like Centos 6.3 or ubuntu 12.04 server with iptable for routing doesn't have any problems with this same setup.
As far as services I use in small office environments --
Generally it's basic firewall / VPN for about 20 users usually no more than 5 concurrent. We also generally use the LAN side DHCP server, the DNS forwader, dynamic dns, and sometimes captive portal at some locations. This box works fine for this setup, except for this issue with the watchdog timeout. The reason to use this type of hardware is that it's readily available and has worked fine with Linux based routers. Also, I can remove the motherboard from the tower enclosure place it in a cheap rack mount atx case and have a good rack mount router/firewall solution.
Or so I thought; I'm sure I can find slightly newer hardware for about the same cost that has PCI-e instead of PCI for the expansion NICs.
Steve -- are your intel NICs PCI?
Thanks for the help!
-
My NICs are all on board so it's hard to say for sure. They may be PCI-X. The bus may not be 33MHz. They are not PCIe though.
The 875p MCH also has the CSA interface which offers 266MB/s again I don't know if this is used or how it would appear in FreeBSD.Steve
-
what model mainboard? sounds interesting.
-
It's a re-purposed Watchguard Firebox X6000. See:
http://forum.pfsense.org/index.php/topic,25011.0.htmlSteve
-
Again, it's not important to have Gigabit speeds, it's just the hardware that I have and that is most available, it's problematic to have to use a 10/100 hub to avoid hard failures.
Generally you can configure a Gigabit capable device to operate at 100Mbps.
For this box at home, I'm going to call it solved unless anyone wants me to experiment to see if we can find the root cause. Again, a straight Linux like Centos 6.3 or ubuntu 12.04 server with iptable for routing doesn't have any problems with this same setup.
I would be interested to see if enabling flow control "fixes" the behaviour. See my earlier reply with a link to another topic for some clues about enabling flow control on the NICs.
-
I agree. Flow control seems like exactly the sort of thing that would solve this, however none of my Intel NICs appear to offer it :-:
[2.0.3-RELEASE][root@pfsense.fire.box]/root(2): ifconfig -m em1 em1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=9b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum>capabilities=100db <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,vlan_hwfilter>ether 00:90:7f:31:4b:ee inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 inet6 fe80::290:7fff:fe31:4bee%em1 prefixlen 64 scopeid 0x2 nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP</full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,polling,vlan_hwcsum,vlan_hwfilter></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum></up,broadcast,running,simplex,multicast>Steve
-
Looks like flow control is not managed in the same way in Intel cards:
http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Flow_ControlThough I'm still seeing nothing. :-\
[2.0.3-RELEASE][root@pfsense.fire.box]/root(1): sysctl hw.em hw.em.eee_setting: 0 hw.em.rx_process_limit: 100 hw.em.enable_msix: 1 hw.em.sbp: 0 hw.em.smart_pwr_down: 0 hw.em.txd: 1024 hw.em.rxd: 1024 hw.em.rx_abs_int_delay: 66 hw.em.tx_abs_int_delay: 66 hw.em.rx_int_delay: 0 hw.em.tx_int_delay: 66Steve
-
However flowcontrol does appear to operational:
[2.0.3-RELEASE][root@pfsense.fire.box]/root(5): sysctl dev.em dev.em.0.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.4 dev.em.0.%driver: em dev.em.0.%location: slot=1 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x1075 subvendor=0x8086 subdevice=0x1075 class=0x020000 dev.em.0.%parent: pci2 dev.em.0.nvm: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 dev.em.0.flow_control: 3 dev.em.0.mbuf_alloc_fail: 0 dev.em.0.cluster_alloc_fail: 0 dev.em.0.dropped: 0 dev.em.0.tx_dma_fail: 0 dev.em.0.tx_desc_fail1: 0 dev.em.0.tx_desc_fail2: 0 dev.em.0.rx_overruns: 0 dev.em.0.watchdog_timeouts: 0 dev.em.0.device_control: 1077674561 dev.em.0.rx_control: 32770 dev.em.0.fc_high_water: 28672 dev.em.0.fc_low_water: 27172 dev.em.0.fifo_workaround: 0 dev.em.0.fifo_reset: 0 dev.em.0.txd_head: 131 dev.em.0.txd_tail: 131 dev.em.0.rxd_head: 194 dev.em.0.rxd_tail: 193 dev.em.0.mac_stats.excess_coll: 0 dev.em.0.mac_stats.single_coll: 0 dev.em.0.mac_stats.multiple_coll: 0 dev.em.0.mac_stats.late_coll: 0 dev.em.0.mac_stats.collision_count: 0 dev.em.0.mac_stats.symbol_errors: 0 dev.em.0.mac_stats.sequence_errors: 0 dev.em.0.mac_stats.defer_count: 0 dev.em.0.mac_stats.missed_packets: 0 dev.em.0.mac_stats.recv_no_buff: 0 dev.em.0.mac_stats.recv_undersize: 0 dev.em.0.mac_stats.recv_fragmented: 0 dev.em.0.mac_stats.recv_oversize: 0 dev.em.0.mac_stats.recv_jabber: 0 dev.em.0.mac_stats.recv_errs: 0 dev.em.0.mac_stats.crc_errs: 0 dev.em.0.mac_stats.alignment_errs: 0 dev.em.0.mac_stats.coll_ext_errs: 0 dev.em.0.mac_stats.xon_recvd: 0 dev.em.0.mac_stats.xon_txd: 0 dev.em.0.mac_stats.xoff_recvd: 0 dev.em.0.mac_stats.xoff_txd: 0 dev.em.0.mac_stats.total_pkts_recvd: 850882 dev.em.0.mac_stats.good_pkts_recvd: 850882 dev.em.0.mac_stats.bcast_pkts_recvd: 699 dev.em.0.mac_stats.mcast_pkts_recvd: 0 dev.em.0.mac_stats.rx_frames_64: 715 dev.em.0.mac_stats.rx_frames_65_127: 847331 dev.em.0.mac_stats.rx_frames_128_255: 985 dev.em.0.mac_stats.rx_frames_256_511: 555 dev.em.0.mac_stats.rx_frames_512_1023: 90 dev.em.0.mac_stats.rx_frames_1024_1522: 1206 dev.em.0.mac_stats.good_octets_recvd: 71709190 dev.em.0.mac_stats.good_octets_txd: 72480859 dev.em.0.mac_stats.total_pkts_txd: 849527 dev.em.0.mac_stats.good_pkts_txd: 849527 dev.em.0.mac_stats.bcast_pkts_txd: 22 dev.em.0.mac_stats.mcast_pkts_txd: 5 dev.em.0.mac_stats.tx_frames_64: 726 dev.em.0.mac_stats.tx_frames_65_127: 846203 dev.em.0.mac_stats.tx_frames_128_255: 152 dev.em.0.mac_stats.tx_frames_256_511: 361 dev.em.0.mac_stats.tx_frames_512_1023: 424 dev.em.0.mac_stats.tx_frames_1024_1522: 1661 dev.em.0.mac_stats.tso_txd: 0 dev.em.0.mac_stats.tso_ctx_fail: 0How do those numbers compare with your failing NIC?
Steve
