Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Em2: watchdog timeout – resetting, plz i need help

    Scheduled Pinned Locked Moved Hardware
    13 Posts 5 Posters 15.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      giorgiolago
      last edited by

      Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these:

      em2: watchdog timeout - resetting
      em2: watchdog timeout - resetting
      em2: watchdog timeout - resetting
      em2: watchdog timeout - resetting

      And the connection falls back repeatedly and indefinitely.
      Searching on google did some tweaks:

      hw.em.rxd = "4096"
      hw.em.txd = "4096"
      hw.em.tx_int_delay = "250"
      hw.em.rx_int_delay = "250"
      hw.em.tx_abs_int_delay = "250"
      hw.em.rx_abs_int_delay = "250"
      hw.em.enable_msix = "0"
      hw.em.msix_queues = "2"
      hw.em.rx_process_limit = "-1"
      hw.em.fc_setting = "0"
      hw.em.num_queues = 1

      I tried several variations, but also without success.

      My infrastructure:

      (7301 cisco router) –---- em1 (pfsense bridge0) em2 ------ sw core cisco catalyst

      I tried also a fresh installation of pfsense 2.0.3 without success.
      My network card is an Intel ® PRO/1000 MT Dual Port Server Adapter PCI-X on a 32-bit PCI slot, operating bridge in 1 <-> em2.
      Motherboard ASUS P8H61-V and CPU corei5, I tried disabling all onboard devices, also without success.
      I have 4 nics identical, tested one per one  all without success also.
      I am using the latest bios from ASUS site, I tried various combinations of bios, also without success.
      I tried to activate the device polling unsuccessfully to solve the problem.
      I tried disable acpi on boot menu but the ser without acpi wont boot.
      I tried disable TOE, FLOW CONTROL, no sucess.

      This is a link to a troughput 60 Mbits with multiple VLANs (more than 200) Wisp provider.
      I tested the same server same hardware but using linux (debian 6) did the bridges, and everything worked properly!, so it is clear that this is a problem software (in intel em driver?)
      Tested on another server (P5VD2MX + Core2Duo) but with the same NIC, and the problem occurs in the same way.
      I realized that it generates a huge number of interruptions em2 over 200 thousand.

      #vmstat -i
      interrupt                          total       rate
      irq16: em1                         12891         40
      irq17: em2                        546630       1713
      irq19: atapci0                      5181         16
      irq23: ehci0 ehci1                  1049          3
      cpu0: timer                       637069       1997
      irq256: em0                         1557          4
      cpu3: timer                       636939       1996
      cpu2: timer                       636939       1996
      cpu1: timer                       636938       1996
      Total                            3115193       9765

      Data for debug:

      [2.0.3-RELEASE] [root@pfsense.localdomain] / root (1): sysctl hw.em
      hw.em.eee_setting: 0
      hw.em.rx_process_limit: 100
      hw.em.enable_msix: 0
      hw.em.sbp: 0
      hw.em.smart_pwr_down: 0
      hw.em.txd: 4096
      hw.em.rxd: 4096
      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: 0

      [2.0.3-RELEASE] [root@pfsense.localdomain] / root (3): sysctl dev.em.2
      dev.em.2.% desc: Intel (R) PRO/1000 Legacy Network Connection 1.0.4
      dev.em.2.% driver: in
      dev.em.2.% location: slot = 0 function = 1
      dev.em.2.% pnpinfo: vendor = 0x8086 device = 0x1079 subvendor = 0x8086 subdevice = 0x1179 class = 0x020000
      dev.em.2.% parent: PCI4
      dev.em.2.nvm: -1
      dev.em.2.rx_int_delay: 0
      dev.em.2.tx_int_delay: 0
      dev.em.2.rx_abs_int_delay: 66
      dev.em.2.tx_abs_int_delay: 66
      dev.em.2.rx_processing_limit: 100
      dev.em.2.flow_control: 0
      dev.em.2.mbuf_alloc_fail: 0
      dev.em.2.cluster_alloc_fail: 0
      dev.em.2.dropped: 0
      dev.em.2.tx_dma_fail: 0
      dev.em.2.tx_desc_fail1: 0
      dev.em.2.tx_desc_fail2: 0
      dev.em.2.rx_overruns: 0
      dev.em.2.watchdog_timeouts: 0
      dev.em.2.device_control: 1076888137
      dev.em.2.rx_control: 32794
      dev.em.2.fc_high_water: 47104
      dev.em.2.fc_low_water: 45604
      dev.em.2.fifo_workaround: 0
      dev.em.2.fifo_reset: 0
      dev.em.2.txd_head: 243
      dev.em.2.txd_tail: 243
      dev.em.2.rxd_head: 1374
      dev.em.2.rxd_tail: 1373
      dev.em.2.mac_stats.excess_coll: 0
      dev.em.2.mac_stats.single_coll: 0
      dev.em.2.mac_stats.multiple_coll: 0
      dev.em.2.mac_stats.late_coll: 0
      dev.em.2.mac_stats.collision_count: 0
      dev.em.2.mac_stats.symbol_errors: 0
      dev.em.2.mac_stats.sequence_errors: 0
      dev.em.2.mac_stats.defer_count: 0
      dev.em.2.mac_stats.missed_packets: 0
      dev.em.2.mac_stats.recv_no_buff: 0
      dev.em.2.mac_stats.recv_undersize: 0
      dev.em.2.mac_stats.recv_fragmented: 0
      dev.em.2.mac_stats.recv_oversize: 0
      dev.em.2.mac_stats.recv_jabber: 0
      dev.em.2.mac_stats.recv_errs: 0
      dev.em.2.mac_stats.crc_errs: 0
      dev.em.2.mac_stats.alignment_errs: 0
      dev.em.2.mac_stats.coll_ext_errs: 0
      dev.em.2.mac_stats.xon_recvd: 0
      dev.em.2.mac_stats.xon_txd: 0
      dev.em.2.mac_stats.xoff_recvd: 0
      dev.em.2.mac_stats.xoff_txd: 0
      dev.em.2.mac_stats.total_pkts_recvd: 6681156
      dev.em.2.mac_stats.good_pkts_recvd: 6681156
      dev.em.2.mac_stats.bcast_pkts_recvd: 17313
      dev.em.2.mac_stats.mcast_pkts_recvd: 156511
      dev.em.2.mac_stats.rx_frames_64: 1199707
      dev.em.2.mac_stats.rx_frames_65_127: 2110104
      dev.em.2.mac_stats.rx_frames_128_255: 396 862
      dev.em.2.mac_stats.rx_frames_256_511: 196001
      dev.em.2.mac_stats.rx_frames_512_1023: 138581
      dev.em.2.mac_stats.rx_frames_1024_1522: 2639901
      dev.em.2.mac_stats.good_octets_recvd: 4439337234
      dev.em.2.mac_stats.good_octets_txd: 15529
      dev.em.2.mac_stats.total_pkts_txd: 143
      dev.em.2.mac_stats.good_pkts_txd: 143
      dev.em.2.mac_stats.bcast_pkts_txd: 104
      dev.em.2.mac_stats.mcast_pkts_txd: 39
      dev.em.2.mac_stats.tx_frames_64: 48
      dev.em.2.mac_stats.tx_frames_65_127: 69
      dev.em.2.mac_stats.tx_frames_128_255: 20
      dev.em.2.mac_stats.tx_frames_256_511: 6
      dev.em.2.mac_stats.tx_frames_512_1023: 0
      dev.em.2.mac_stats.tx_frames_1024_1522: 0
      dev.em.2.mac_stats.tso_txd: 0
      dev.em.2.mac_stats.tso_ctx_fail: 0

      #uname -a
      FreeBSD pfsense.localdomain 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013     root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  amd64

      Pciconf-lvc:

      em1 @ pci0: 4:0:0: class = 0x020000 card = 0x11798086 chip = 0x10798086 rev = 0x03 hdr = 0x00
         class = network
         subclass = ethernet
         cap 01 [dc] = powerspec 2 supports D0 D3 current D0
         cap 07 [e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction
      em2 @ pci0: 4:0:1: class = 0x020000 card = 0x11798086 chip = 0x10798086 rev = 0x03 hdr = 0x00
         class = network
         subclass = ethernet
         cap 01 [dc] = powerspec 2 supports D0 D3 current D0
         cap 07 [e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction

      dmesg:
      Copyright © 1992-2010 The FreeBSD Project.
      Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
      The Regents of the University of California. All rights reserved.
      FreeBSD is a registered trademark of The FreeBSD Foundation.
      FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013
          root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
      Timecounter "i8254" frequency 1193182 Hz quality 0
      CPU: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz (2892.73-MHz K8-class CPU)
        Origin = "GenuineIntel"  Id = 0x206a7  Family = 6  Model = 2a  Stepping = 7
        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=0x179ae3bf<sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17>,SSE4.1,SSE4.2,POPCNT,<b24>,AESNI,XSAVE,<b28>>
        AMD Features=0x28100800 <syscall,nx,rdtscp,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
      real memory  = 8589934592 (8192 MB)
      avail memory = 7952838656 (7584 MB)
      ACPI APIC Table: <alaska a="" m="" i="">FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
      FreeBSD/SMP: 1 package(s) x 4 core(s)
      cpu0 (BSP): APIC ID:  0
      cpu1 (AP): APIC ID:  2
      cpu2 (AP): APIC ID:  4
      cpu3 (AP): APIC ID:  6
      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: <alaska a="" m="" i="">on motherboard
      acpi0: [ITHREAD]
      ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND
      ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20100331/nsinit-442)
      acpi0: Power Button (fixed)
      acpi0: reservation of 67, 1 (4) failed
      Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
      acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
      cpu0: <acpi cpu="">on acpi0
      cpu1: <acpi cpu="">on acpi0
      cpu2: <acpi cpu="">on acpi0
      cpu3: <acpi cpu="">on acpi0
      acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
      Timecounter "HPET" frequency 14318180 Hz quality 900
      pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
      pci0: <acpi pci="" bus="">on pcib0
      pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0
      pci1: <acpi pci="" bus="">on pcib1
      vgapci0: <vga-compatible display="">port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
      pci0: <simple comms="">at device 22.0 (no driver attached)
      ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xf7f04000-0xf7f043ff irq 23 at device 26.0 on pci0
      ehci0: [ITHREAD]
      usbus0: EHCI version 1.0
      usbus0: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
      pcib2: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
      pci2: <acpi pci="" bus="">on pcib2
      em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xe000-0xe01f mem 0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2
      em0: Using an MSI interrupt
      em0: [FILTER]
      pcib3: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
      pci3: <acpi pci="" bus="">on pcib3
      pcib4: <acpi pci-pci="" bridge="">irq 16 at device 0.0 on pci3
      pci4: <acpi pci="" bus="">on pcib4
      em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xd040-0xd07f mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci4
      em1: [FILTER]
      em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xd000-0xd03f mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci4
      em2: [FILTER]
      ehci1: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xf7f03000-0xf7f033ff irq 23 at device 29.0 on pci0
      ehci1: [ITHREAD]
      usbus1: EHCI version 1.0
      usbus1: <ehci (generic)="" usb="" 2.0="" controller="">on ehci1
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel ahci="" controller="">port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0
      atapci0: [ITHREAD]
      atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported
      ata2: <ata 0="" channel="">on atapci0
      ata2: [ITHREAD]
      ata3: <ata 1="" channel="">on atapci0
      ata3: [ITHREAD]
      pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
      acpi_button0: <power button="">on acpi0
      acpi_tz0: <thermal zone="">on acpi0
      acpi_tz1: <thermal zone="">on acpi0
      atrtc0: <at realtime="" clock="">port 0x70-0x77 irq 8 on acpi0
      atrtc0: Warning: Couldn't map I/O.
      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
      atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
      atkbd0: <at keyboard="">irq 1 on atkbdc0
      kbd0 at atkbd0
      atkbd0: [GIANT-LOCKED]
      atkbd0: [ITHREAD]
      ppc0: cannot reserve I/O port range
      coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
      est0: <enhanced speedstep="" frequency="" control="">on cpu0
      p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
      coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1
      est1: <enhanced speedstep="" frequency="" control="">on cpu1
      p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
      coretemp2: <cpu on-die="" thermal="" sensors="">on cpu2
      est2: <enhanced speedstep="" frequency="" control="">on cpu2
      p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
      coretemp3: <cpu on-die="" thermal="" sensors="">on cpu3
      est3: <enhanced speedstep="" frequency="" control="">on cpu3
      p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
      Timecounters tick every 1.000 msec
      IPsec: Initialized Security Association Processing.
      usbus0: 480Mbps High Speed USB v2.0
      usbus1: 480Mbps High Speed USB v2.0
      ad4: 476940MB <seagate st3500418as="" cc35="">at ata2-master UDMA100 SATA 3Gb/s
      ugen0.1: <intel>at usbus0
      uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
      ugen1.1: <intel>at usbus1
      uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
      acd0: DVDR <atapi ihas124="" c="" ll02="">at ata3-master UDMA100 SATA 1.5Gb/s
      SMP: AP CPU #1 Launched!
      SMP: AP CPU #3 Launched!
      SMP: AP CPU #2 Launched!
      Root mount waiting for: usbus1 usbus0
      uhub0: 2 ports with 2 removable, self powered
      uhub1: 2 ports with 2 removable, self powered
      Root mount waiting for: usbus1 usbus0
      ugen0.2: <vendor 0x8087="">at usbus0
      uhub2: <vendor 2="" 9="" 0x8087="" product="" 0x0024,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
      ugen1.2: <vendor 0x8087="">at usbus1
      uhub3: <vendor 2="" 9="" 0x8087="" product="" 0x0024,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus1
      Root mount waiting for: usbus1 usbus0
      uhub2: 4 ports with 4 removable, self powered
      uhub3: 6 ports with 6 removable, self powered
      ugen0.3: <usb>at usbus0
      ukbd0: <usb 0="" 3="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus0
      kbd2 at ukbd0
      uhid0: <usb 0="" 3="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus0
      Trying to mount root from ufs:/dev/ad4s1a
      pflog0: promiscuous mode enabled
      em2: link state changed to UP
      bridge0: promiscuous mode enabled
      pflog0: promiscuous mode disabled
      Waiting (max 60 seconds) for system process vnlru' to stop…done Waiting (max 60 seconds) for system process bufdaemon' to stop...done
      Waiting (max 60 seconds) for system process `syncer' to stop...
      Syncing disks, vnodes remaining...0 0 0 done
      All buffers synced.
      Copyright (c) 1992-2010 The FreeBSD Project.
      Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
      The Regents of the University of California. All rights reserved.
      FreeBSD is a registered trademark of The FreeBSD Foundation.
      FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013
          root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
      Timecounter "i8254" frequency 1193182 Hz quality 0
      CPU: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz (2892.72-MHz K8-class CPU)
        Origin = "GenuineIntel"  Id = 0x206a7  Family = 6  Model = 2a  Stepping = 7
        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=0x179ae3bf<sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17>,SSE4.1,SSE4.2,POPCNT,<b24>,AESNI,XSAVE,<b28>>
        AMD Features=0x28100800 <syscall,nx,rdtscp,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
      real memory  = 8589934592 (8192 MB)
      avail memory = 7952838656 (7584 MB)
      ACPI APIC Table: <alaska a="" m="" i="">FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
      FreeBSD/SMP: 1 package(s) x 4 core(s)
      cpu0 (BSP): APIC ID:  0
      cpu1 (AP): APIC ID:  2
      cpu2 (AP): APIC ID:  4
      cpu3 (AP): APIC ID:  6
      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: <alaska a="" m="" i="">on motherboard
      acpi0: [ITHREAD]
      ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND
      ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20100331/nsinit-442)
      acpi0: Power Button (fixed)
      acpi0: reservation of 67, 1 (4) failed
      Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
      acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
      cpu0: <acpi cpu="">on acpi0
      cpu1: <acpi cpu="">on acpi0
      cpu2: <acpi cpu="">on acpi0
      cpu3: <acpi cpu="">on acpi0
      acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
      Timecounter "HPET" frequency 14318180 Hz quality 900
      pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
      pci0: <acpi pci="" bus="">on pcib0
      pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0
      pci1: <acpi pci="" bus="">on pcib1
      vgapci0: <vga-compatible display="">port 0xf000-0xf03f mem 0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
      pci0: <simple comms="">at device 22.0 (no driver attached)
      ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xf7f04000-0xf7f043ff irq 23 at device 26.0 on pci0
      ehci0: [ITHREAD]
      usbus0: EHCI version 1.0
      usbus0: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
      pcib2: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
      pci2: <acpi pci="" bus="">on pcib2
      em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xe000-0xe01f mem 0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2
      em0: Using an MSI interrupt
      em0: [FILTER]
      pcib3: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
      pci3: <acpi pci="" bus="">on pcib3
      pcib4: <acpi pci-pci="" bridge="">irq 16 at device 0.0 on pci3
      pci4: <acpi pci="" bus="">on pcib4
      em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xd040-0xd07f mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci4
      em1: [FILTER]
      em2: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.4="">port 0xd000-0xd03f mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci4
      em2: [FILTER]
      ehci1: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xf7f03000-0xf7f033ff irq 23 at device 29.0 on pci0
      ehci1: [ITHREAD]
      usbus1: EHCI version 1.0
      usbus1: <ehci (generic)="" usb="" 2.0="" controller="">on ehci1
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel ahci="" controller="">port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0
      atapci0: [ITHREAD]
      atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported
      ata2: <ata 0="" channel="">on atapci0
      ata2: [ITHREAD]
      ata3: <ata 1="" channel="">on atapci0
      ata3: [ITHREAD]
      pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
      acpi_button0: <power button="">on acpi0
      acpi_tz0: <thermal zone="">on acpi0
      acpi_tz1: <thermal zone="">on acpi0
      atrtc0: <at realtime="" clock="">port 0x70-0x77 irq 8 on acpi0
      atrtc0: Warning: Couldn't map I/O.
      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
      atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
      atkbd0: <at keyboard="">irq 1 on atkbdc0
      kbd0 at atkbd0
      atkbd0: [GIANT-LOCKED]
      atkbd0: [ITHREAD]
      ppc0: cannot reserve I/O port range
      coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
      est0: <enhanced speedstep="" frequency="" control="">on cpu0
      p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
      coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1
      est1: <enhanced speedstep="" frequency="" control="">on cpu1
      p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
      coretemp2: <cpu on-die="" thermal="" sensors="">on cpu2
      est2: <enhanced speedstep="" frequency="" control="">on cpu2
      p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
      coretemp3: <cpu on-die="" thermal="" sensors="">on cpu3
      est3: <enhanced speedstep="" frequency="" control="">on cpu3
      p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
      Timecounters tick every 1.000 msec
      IPsec: Initialized Security Association Processing.
      usbus0: 480Mbps High Speed USB v2.0
      usbus1: 480Mbps High Speed USB v2.0
      ad4: 476940MB <seagate st3500418as="" cc35="">at ata2-master UDMA100 SATA 3Gb/s
      ugen0.1: <intel>at usbus0
      uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
      ugen1.1: <intel>at usbus1
      uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
      acd0: DVDR <atapi ihas124="" c="" ll02="">at ata3-master UDMA100 SATA 1.5Gb/s
      SMP: AP CPU #3 Launched!
      SMP: AP CPU #2 Launched!
      SMP: AP CPU #1 Launched!
      Root mount waiting for: usbus1 usbus0
      uhub0: 2 ports with 2 removable, self powered
      uhub1: 2 ports with 2 removable, self powered
      Root mount waiting for: usbus1 usbus0
      ugen0.2: <vendor 0x8087="">at usbus0
      uhub2: <vendor 2="" 9="" 0x8087="" product="" 0x0024,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
      ugen1.2: <vendor 0x8087="">at usbus1
      uhub3: <vendor 2="" 9="" 0x8087="" product="" 0x0024,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus1
      uhub2: 4 ports with 4 removable, self powered
      uhub3: 6 ports with 6 removable, self powered
      Root mount waiting for: usbus0
      ugen0.3: <usb>at usbus0
      ukbd0: <usb 0="" 3="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus0
      kbd2 at ukbd0
      uhid0: <usb 0="" 3="" usb="" keykoard,="" class="" 0,="" rev="" 1.10="" 1.10,="" addr="">on usbus0
      Trying to mount root from ufs:/dev/ad4s1a
      pflog0: promiscuous mode enabled
      em2: link state changed to UP
      bridge0: promiscuous mode enabled
      em1: link state changed to UP
      em1: Watchdog timeout – resetting
      em1: link state changed to DOWN
      em1: link state changed to UP
      em1: Watchdog timeout -- resetting
      em1: link state changed to DOWN</usb></usb></usb></vendor></vendor></vendor></vendor></atapi></intel></intel></intel></intel></seagate></cpu></enhanced></cpu></cpu></enhanced></cpu></cpu></enhanced></cpu></cpu></enhanced></cpu></at></keyboard></generic></system></at></thermal></thermal></power></serial></ata></ata></intel></isa></pci-isa></ehci></ehci></intel(r)></intel(r)></acpi></acpi></acpi></acpi></intel(r)></acpi></acpi></ehci></ehci></simple></vga-compatible></acpi></acpi></acpi></acpi></high></acpi></acpi></acpi></acpi></alaska></software></version></alaska></lahf></syscall,nx,rdtscp,lm></b28></b24></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17></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></usb></usb></usb></vendor></vendor></vendor></vendor></atapi></intel></intel></intel></intel></seagate></cpu></enhanced></cpu></cpu></enhanced></cpu></cpu></enhanced></cpu></cpu></enhanced></cpu></at></keyboard></generic></system></at></thermal></thermal></power></serial></ata></ata></intel></isa></pci-isa></ehci></ehci></intel(r)></intel(r)></acpi></acpi></acpi></acpi></intel(r)></acpi></acpi></ehci></ehci></simple></vga-compatible></acpi></acpi></acpi></acpi></high></acpi></acpi></acpi></acpi></alaska></software></version></alaska></lahf></syscall,nx,rdtscp,lm></b28></b24></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17></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>

      1 Reply Last reply Reply Quote 0
      • ?
        A Former User
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • K
          KrPacMan
          last edited by

          I had the Watchdog timeout-problem with the msk driver, i solved it by adding the following to /boot/loader.conf

          hw.msk.msi_disable="1"
          hw.pci.enable_msi=0
          hw.pci.enable_msix=0

          Don't know if that will solve your problem, but probably worth a try.

          Panda GateDefender Performa 8100 (Portwell NR-5500) with Pfsense 2.1 :: blog

          1 Reply Last reply Reply Quote 0
          • G
            giorgiolago
            last edited by

            I gave up intel nic, and bought a HP NC382T nic Broadcom 5709, my god! It is the same problem! What can this be? Did I data traffic is not supported by pfSense? :'(

            bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7273): Watchdog timeout occurred, resetting!
            bce0: link state changed to DOWN
            bce0: link state changed to UP
            bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7273): Watchdog timeout occurred, resetting!
            bce0: link state changed to DOWN
            bce0: link state changed to UP
            bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7273): Watchdog timeout occurred, resetting!
            bce0: 2 link states coalesced
            bce0: link state changed to UP
            bce0: link state changed to DOWN
            bce0: link state changed to UP
            bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7273): Watchdog timeout occurred, resetting!
            bce0: link state changed to DOWN
            bce0: link state changed to UP
            bce0: /usr/pfSensesrc/src/sys/dev/bce/if_bce.c(7273): Watchdog timeout occurred, resetting!
            bce0: link state changed to DOWN

            1 Reply Last reply Reply Quote 0
            • G
              giorgiolago
              last edited by

              discovered something very important, if I disable pf (pfctl-d) the error watchdog timetout ends! I'm almost to the solution of the problem, which can be guys?

              1 Reply Last reply Reply Quote 0
              • G
                giorgiolago
                last edited by

                I found the problem, strangely when I activate filtering on the bridge members (# sysctl net.link.bridge.pfil_member: 1) errors watchdog timeout end! :o I would not want to use filtering bridge members as the firewall rules are more complex, does anyone know how to solve this?

                1 Reply Last reply Reply Quote 0
                • G
                  giorgiolago
                  last edited by

                  anyone ?  :'(

                  1 Reply Last reply Reply Quote 0
                  • W
                    wallabybob
                    last edited by

                    I'm running a bridge on a wired interface and a WiFi interface in pfSense 2.0.1 with filtering on the bridge and I don't see watchdog timeout errors. Therefore I don't think what you are seeing is something tied to filtering on a bridge or its members.

                    I second the suggestion: @SunCatalyst:

                    have you Tried any of the Pfsense 2.1-Beta releases to see if things are any better?

                    pfSense 2.1 builds have much more up to date device drivers than the 2.0.x builds.

                    1 Reply Last reply Reply Quote 0
                    • G
                      giorgiolago
                      last edited by

                      @wallabybob:

                      I'm running a bridge on a wired interface and a WiFi interface in pfSense 2.0.1 with filtering on the bridge and I don't see watchdog timeout errors. Therefore I don't think what you are seeing is something tied to filtering on a bridge or its members.

                      I second the suggestion: @SunCatalyst:

                      have you Tried any of the Pfsense 2.1-Beta releases to see if things are any better?

                      pfSense 2.1 builds have much more up to date device drivers than the 2.0.x builds.

                      how not? if I disable pf (pfctl-d) or add filtering on bridge members the problem goes away?
                      I tested version 2.0.3 and 2.1RC0 same problems …

                      1 Reply Last reply Reply Quote 0
                      • G
                        giorgiolago
                        last edited by

                        bump

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Disabling pf altogether will dramatically reduce the loading on the CPU which might explain why you don't see timeouts in that case.

                          Leaving filtering on the bridge members is harder to explain. Perhaps in doing that you are better able to take advantage of hardware off loading features on the NICs. Since the bridge interface is done in software it has no off loading. This could result in a higher cpu load and eventual timeouts. That's speculation though.

                          Neither of those seems very likely as your i5 should have no problems. Since you have seen the same problem across different NICs it does appear that some feature of your motherboard/chipset is not working well with FreeBSD. It seems that maybe your board/cpu is not servicing interrupts either at all or fast enough under some conditions. I would probably try disabling MSI or MSI-X to see if that effects the situation at all.

                          hw.pci.enable_msi=0
                          hw.pci.enable_msix=0
                          

                          If it is some incompatibility between FreeBSD and that board someone else will probably have already seen it.

                          Steve

                          Edit: I assume this is you? http://freebsd.1045724.n5.nabble.com/em2-watchdog-timeout-resetting-td5813842.html

                          1 Reply Last reply Reply Quote 0
                          • G
                            giorgiolago
                            last edited by

                            1-I am using filter in bridge members, was the only solution I found to the problem ….
                            I used another motherboard with different chipset and has the same problem, I think pfsense can not process a trunk link with a large number of VLANs... my opinion.
                            2 - yes I am :)

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              There have been reports of using, successfully, 1000+ VLANs with pfSense so it's not a problem with that directly. Perhaps some combination of a large number or VLANs and interface bridging?  :-
                              Did you try any of the suggestions from the FreeBSD lists?

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.