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

    Multi-lan config problem?

    2.0-RC Snapshot Feedback and Problems - RETIRED
    6
    17
    10.2k
    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.
    • L
      littlejohn
      last edited by

      Hello,

      I'm slowly getting back up to speed with a fresh install (2.0-BETA4 (amd64)  built on Fri Nov 12 18:33:07 UTC 2010 FreeBSD 8.1-RELEASE-p1) but I'm stuck with a multi-lan configuration and can't figure out what I'm doing wrong. Worse yet, I had this running before.

      Setup is R310 with two Intel Gigabit ET Quad Port Server Adapter, x4 PCIe (igb0-igb3, igb4-igb7)

      Quick description: Installed from scratch, WAN is igb0 (DHCP), LAN is igb3 (172.20.3.1/24), OPT1 is igb1 (172.20.1.1/24). Rules are default allow LAN to any, allow OPT1 to any.
      LAN: one other machine 172.20.3.20
      OPT1: one other machine 172.20.1.10

      on LAN: can ping both 172.20.3.1 and 172.20.1.1 from 172.20.3.20, NAT working as far as I can tell.
      on OPT1: 172.20.1.10 cannot ping 172.20.1.1, 172.20.3.1 and 172.20.3.20

      from the firewall console:

      PING 172.20.1.10 (172.20.1.10): 56 data bytes
      ping: sendto: Network is down

      which is different from pinging a non-existent machine on LAN:

      PING 172.20.3.21 (172.20.3.21): 56 data bytes
      ping: sendto: Host is down

      ifconfig on the console (addresses changed to protect the innocent):

      igb1: flags=8803 <up,broadcast,simplex,multicast>metric 0 mtu 1500
      options=bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum>ether 00:1b:21:00:00:d1
      inet6 feff::21b:20ff:fe6a:00d1%igb1 prefixlen 64 scopeid 0x2
      inet 172.20.1.1 netmask 0xffffff00 broadcast 172.20.1.255
      nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
      status: active

      igb3: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
      options=bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum>ether 00:1b:21:00:00:d5
      inet6 feff::21b:20ff:fe6a:00d5%igb3 prefixlen 64 scopeid 0x4
      inet 172.20.3.1 netmask 0xffffff00 broadcast 172.20.3.255
      nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
      status: active

      I'm also attaching some (hopefully) relevant screenshots. Any help welcome!

      Regards,
      John

      screenshot_1.png
      screenshot_1.png_thumb
      screenshot_2.png
      screenshot_2.png_thumb
      screenshot_3.png
      screenshot_3.png_thumb
      screenshot_4.png
      screenshot_4.png_thumb
      screenshot_5.png
      screenshot_5.png_thumb</full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum></up,broadcast,simplex,multicast>

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

        The status of your interfaces shows:

        igb1: flags=8803 <up,broadcast,simplex,multicast>metric 0 mtu 1500

        igb3: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500</up,broadcast,running,simplex,multicast></up,broadcast,simplex,multicast>

        igb1 is not "running", igb3 is. Something is not quite right with igb1. Maybe its the hardware, maybe its the cable. Suggest you try swapping cables and see if the fault moves.

        1 Reply Last reply Reply Quote 0
        • L
          littlejohn
          last edited by

          Thanks wallabybob, I'll swap the cables and IPs tomorrow.

          Although I'm pretty sure it's not the hardware as I had the setup working up until Nov 5th (lost the config unfortunately, but I'm learning…).

          Regards,
          John

          1 Reply Last reply Reply Quote 0
          • L
            littlejohn
            last edited by

            Hello,

            I've swapped the IP addresses / cables round, I'm confident that's not the problem.

            Anything else I can check?

            Regards,
            John

            1 Reply Last reply Reply Quote 0
            • C
              clarknova
              last edited by

              What does your Outbound NAT page look like?

              Does 172.20.1.10 have a default route?

              db

              1 Reply Last reply Reply Quote 0
              • T
                toomeek
                last edited by

                I don't know is this causing this, but is "Block private networks" checked for LAN interfaces?

                pfsense_test.png
                pfsense_test.png_thumb

                1 Reply Last reply Reply Quote 0
                • L
                  littlejohn
                  last edited by

                  Hi all,

                  First, thanks for the suggestions clarknova and TooMeeK, but I've narrowed it down to a kernel issue with the igb driver.

                  This is what I know:

                  • The Intel Gigabit ET Quad Port Server Adapter, x4 PCIe  uses the igb driver.
                  • on my setup: igb0 is WAN.
                  • From factory reset, whichever igb1-3 I define next will be up, and a valid network can be associated with the interface. DHCP, etc, will work as intended.
                  • If I add more than two interfaces (other than WAN, LAN), the subsequently defined interfaces/network will be down (see symptoms described above).
                  • ifconfig shows the RUNNING flag for WAN,LAN but not for the other interfaces (see above)
                  • I will also get "igb2: Could not setup receive structures" type kernel errors. (same for igb3 or any other interface I add next)

                  Now, I found this page: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-10/msg00267.html which describes the receive structures problem and a possible solution.

                  Anyone can help / guide me further? Anyone knows what the score is with the igb driver?

                  Regards,
                  (distraught) John

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

                    The referenced page says The problem is mbuf resources, the driver is autoconfiguring the number of queues based on the number of cores, on newer systems with lots of them this is outstripping the mbuf resource pool.

                    If you need to use more than the two interfaces a temporary workaround might be to use the uniprocessor kernel to test to see how many more interfaces you can get operational. I'm not familiar with the CPU(s) in your system so I don't know if this is relevant: FreeBSD used to (still does?) have a mechanism to disable hyperthreading, thus reducing the number of operational CPU cores. Either way you could try reducing the number of cores seen by the OS to see if that helps reduce the resource demands so you can get more interfaces operational.

                    To make the suggested change would probably involve setting up a pfSense build environment and building your own kernel or you might be able to persuade the pfSense developers to

                    • make the suggested change or

                    • add a sysctl to the igb driver to allow the num_queues variable to be changed at boot time or

                    • revert to the igb driver from FreeBSD 8.1 RELEASE

                    1 Reply Last reply Reply Quote 0
                    • L
                      littlejohn
                      last edited by

                      Hi wallabybob,

                      hope this is relevant, I did a tar xzpf /kernels/kernel_uniprocessor.gz -C /boot/ as per http://doc.pfsense.org/index.php/Switching_Kernels

                      
Nov 21 16:07:04 pfSense syslogd: kernel boot file is /boot/kernel/kernel
Nov 21 16:07:04 pfSense kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Nov 21 16:07:04 pfSense kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 21 16:07:04 pfSense kernel: The Regents of the University of California. All rights reserved.
Nov 21 16:07:04 pfSense kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 21 16:07:04 pfSense kernel: FreeBSD 8.1-RELEASE-p1 #1: Sat Nov 20 08:16:31 UTC 2010
Nov 21 16:07:04 pfSense kernel: sullrich@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 amd64
Nov 21 16:07:04 pfSense kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 21 16:07:04 pfSense kernel: CPU: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz (1862.00-MHz K8-class CPU)
Nov 21 16:07:04 pfSense kernel: Origin = "GenuineIntel"  Id = 0x106e5  Family = 6  Model = 1e  Stepping = 5
Nov 21 16:07:04 pfSense kernel: 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>Nov 21 16:07:04 pfSense kernel: Features2=0x98e3fd <sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt>Nov 21 16:07:04 pfSense kernel: AMD Features=0x28100800 <syscall,nx,rdtscp,lm>Nov 21 16:07:04 pfSense kernel: AMD Features2=0x1 <lahf>Nov 21 16:07:04 pfSense kernel: TSC: P-state invariant
Nov 21 16:07:04 pfSense kernel: real memory  = 2147483648 (2048 MB)
Nov 21 16:07:04 pfSense kernel: avail memory = 2042900480 (1948 MB)
Nov 21 16:07:04 pfSense kernel: ACPI APIC Table: <dell  pe_sc3 ="">Nov 21 16:07:04 pfSense kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Nov 21 16:07:04 pfSense kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
Nov 21 16:07:04 pfSense kernel: cpu0 (BSP): APIC ID:  0
Nov 21 16:07:04 pfSense kernel: cpu1 (AP): APIC ID:  1
Nov 21 16:07:04 pfSense kernel: cpu2 (AP): APIC ID:  2
Nov 21 16:07:04 pfSense kernel: cpu3 (AP): APIC ID:  3
Nov 21 16:07:04 pfSense kernel: cpu4 (AP): APIC ID:  4
Nov 21 16:07:04 pfSense kernel: cpu5 (AP): APIC ID:  5
Nov 21 16:07:04 pfSense kernel: cpu6 (AP): APIC ID:  6
Nov 21 16:07:04 pfSense kernel: cpu7 (AP): APIC ID:  7
Nov 21 16:07:04 pfSense kernel: ioapic0 <version 2.0="">irqs 0-23 on motherboard
Nov 21 16:07:04 pfSense kernel: wlan: mac acl policy registered
Nov 21 16:07:04 pfSense kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 21 16:07:04 pfSense kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 21 16:07:04 pfSense kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff804608a0, 0) error 1
Nov 21 16:07:04 pfSense kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 21 16:07:04 pfSense kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 21 16:07:04 pfSense kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80460940, 0) error 1
Nov 21 16:07:04 pfSense kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
Nov 21 16:07:04 pfSense kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
Nov 21 16:07:04 pfSense kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806447d0, 0) error 1
Nov 21 16:07:04 pfSense kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 21 16:07:04 pfSense kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 21 16:07:04 pfSense kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff804609e0, 0) error 1
Nov 21 16:07:04 pfSense kernel: kbd1 at kbdmux0
Nov 21 16:07:04 pfSense kernel: cryptosoft0: <software crypto="">on motherboard
Nov 21 16:07:04 pfSense kernel: padlock0: No ACE support.
Nov 21 16:07:04 pfSense kernel: acpi0: <dell pe_sc3="">on motherboard
Nov 21 16:07:04 pfSense kernel: acpi0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: acpi0: Power Button (fixed)
Nov 21 16:07:04 pfSense kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Nov 21 16:07:04 pfSense kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
Nov 21 16:07:04 pfSense kernel: cpu0: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu1: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu2: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu3: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu4: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu5: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu6: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: cpu7: <acpi cpu="">on acpi0
Nov 21 16:07:04 pfSense kernel: acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
Nov 21 16:07:04 pfSense kernel: Timecounter "HPET" frequency 14318180 Hz quality 900
Nov 21 16:07:04 pfSense kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
Nov 21 16:07:04 pfSense kernel: pci0: <acpi pci="" bus="">on pcib0
Nov 21 16:07:04 pfSense kernel: pcib1: <acpi pci-pci="" bridge="">at device 3.0 on pci0
Nov 21 16:07:04 pfSense kernel: pci4: <acpi pci="" bus="">on pcib1
Nov 21 16:07:04 pfSense kernel: pcib2: <pci-pci bridge="">at device 0.0 on pci4
Nov 21 16:07:04 pfSense kernel: pci5: <pci bus="">on pcib2
Nov 21 16:07:04 pfSense kernel: pcib3: <pci-pci bridge="">at device 2.0 on pci5
Nov 21 16:07:04 pfSense kernel: pci6: <pci bus="">on pcib3
Nov 21 16:07:04 pfSense kernel: igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xfcc0-0xfcdf mem 0xddfc0000-0xddfdffff,0xde000000-0xde3fffff,0xddfb8000-0xddfbbfff irq 18 at device 0.0 on pci6
Nov 21 16:07:04 pfSense kernel: igb0: Using MSIX interrupts with 9 vectors
Nov 21 16:07:04 pfSense kernel: igb0: [ITHREAD]
Nov 21 16:07:04 pfSense last message repeated 8 times
Nov 21 16:07:04 pfSense kernel: igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xfce0-0xfcff mem 0xddfe0000-0xddffffff,0xde400000-0xde7fffff,0xddfbc000-0xddfbffff irq 19 at device 0.1 on pci6
Nov 21 16:07:04 pfSense kernel: igb1: Using MSIX interrupts with 9 vectors
Nov 21 16:07:04 pfSense kernel: igb1: [ITHREAD]
Nov 21 16:07:04 pfSense last message repeated 8 times
Nov 21 16:07:04 pfSense kernel: pcib4: <pci-pci bridge="">at device 4.0 on pci5
Nov 21 16:07:04 pfSense kernel: pci7: <pci bus="">on pcib4
Nov 21 16:07:04 pfSense kernel: igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xecc0-0xecdf mem 0xdd3c0000-0xdd3dffff,0xdd400000-0xdd7fffff,0xdd3b8000-0xdd3bbfff irq 16 at device 0.0 on pci7
Nov 21 16:07:04 pfSense kernel: igb2: Using MSIX interrupts with 9 vectors
Nov 21 16:07:04 pfSense kernel: igb2: [ITHREAD]
Nov 21 16:07:04 pfSense last message repeated 8 times
Nov 21 16:07:04 pfSense kernel: igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xece0-0xecff mem 0xdd3e0000-0xdd3fffff,0xdd800000-0xddbfffff,0xdd3bc000-0xdd3bffff irq 17 at device 0.1 on pci7
Nov 21 16:07:04 pfSense kernel: igb3: Using MSIX interrupts with 9 vectors
Nov 21 16:07:04 pfSense kernel: igb3: [ITHREAD]
Nov 21 16:07:04 pfSense last message repeated 8 times
Nov 21 16:07:04 pfSense kernel: pcib5: <acpi pci-pci="" bridge="">at device 5.0 on pci0
Nov 21 16:07:04 pfSense kernel: pci8: <acpi pci="" bus="">on pcib5
Nov 21 16:07:04 pfSense kernel: ath0: <atheros 5416="">mem 0xde9f0000-0xde9fffff irq 16 at device 0.0 on pci8
Nov 21 16:07:04 pfSense kernel: ath0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: ath0: AR5418 mac 12.10 RF2133 phy 8.1
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 8.0 (no driver attached)
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 8.1 (no driver attached)
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 8.2 (no driver attached)
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 8.3 (no driver attached)
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 16.0 (no driver attached)
Nov 21 16:07:04 pfSense kernel: pci0: <base peripheral=""> at device 16.1 (no driver attached)
Nov 21 16:07:04 pfSense kernel: ehci0: <intel pch="" usb="" 2.0="" controller="" usb-b="">mem 0xde8fc000-0xde8fc3ff irq 22 at device 26.0 on pci0
Nov 21 16:07:04 pfSense kernel: ehci0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: usbus0: EHCI version 1.0
Nov 21 16:07:04 pfSense kernel: usbus0: <intel pch="" usb="" 2.0="" controller="" usb-b="">on ehci0
Nov 21 16:07:04 pfSense kernel: pcib6: <acpi pci-pci="" bridge="">at device 28.0 on pci0
Nov 21 16:07:04 pfSense kernel: pci3: <acpi pci="" bus="">on pcib6
Nov 21 16:07:04 pfSense kernel: pcib7: <acpi pci-pci="" bridge="">at device 28.4 on pci0
Nov 21 16:07:04 pfSense kernel: pci2: <acpi pci="" bus="">on pcib7
Nov 21 16:07:04 pfSense kernel: bce0: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xd8000000-0xd9ffffff irq 16 at device 0.0 on pci2
Nov 21 16:07:04 pfSense kernel: miibus0: <mii bus="">on bce0
Nov 21 16:07:04 pfSense kernel: brgphy0: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus0
Nov 21 16:07:04 pfSense kernel: brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 21 16:07:04 pfSense kernel: bce0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: bce0: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.2); Flags (MSI|MFW); MFW (NCSI 2.0.8)
Nov 21 16:07:04 pfSense kernel: bce1: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xda000000-0xdbffffff irq 17 at device 0.1 on pci2
Nov 21 16:07:04 pfSense kernel: miibus1: <mii bus="">on bce1
Nov 21 16:07:04 pfSense kernel: brgphy1: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus1
Nov 21 16:07:04 pfSense kernel: brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 21 16:07:04 pfSense kernel: bce1: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: bce1: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.2); Flags (MSI|MFW); MFW (NCSI 2.0.8)
Nov 21 16:07:04 pfSense kernel: ehci1: <intel pch="" usb="" 2.0="" controller="" usb-a="">mem 0xde8fe000-0xde8fe3ff irq 22 at device 29.0 on pci0
Nov 21 16:07:04 pfSense kernel: ehci1: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: usbus1: EHCI version 1.0
Nov 21 16:07:04 pfSense kernel: usbus1: <intel pch="" usb="" 2.0="" controller="" usb-a="">on ehci1
Nov 21 16:07:04 pfSense kernel: pcib8: <acpi pci-pci="" bridge="">at device 30.0 on pci0
Nov 21 16:07:04 pfSense kernel: pci1: <acpi pci="" bus="">on pcib8
Nov 21 16:07:04 pfSense kernel: vgapci0: <vga-compatible display="">mem 0xd7800000-0xd7ffffff,0xdc7fc000-0xdc7fffff,0xdc800000-0xdcffffff irq 19 at device 3.0 on pci1
Nov 21 16:07:04 pfSense kernel: isab0: <pci-isa bridge="">at device 31.0 on pci0
Nov 21 16:07:04 pfSense kernel: isa0: <isa bus="">on isab0
Nov 21 16:07:04 pfSense kernel: atapci0: <intel pch="" sata300="" controller="">port 0xdca0-0xdca7,0xdc90-0xdc93,0xdca8-0xdcaf,0xdc94-0xdc97,0xdcc0-0xdccf,0xdcd0-0xdcdf irq 20 at device 31.2 on pci0
Nov 21 16:07:04 pfSense kernel: atapci0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: ata2: <ata 0="" channel="">on atapci0
Nov 21 16:07:04 pfSense kernel: ata2: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: ata3: <ata 1="" channel="">on atapci0
Nov 21 16:07:04 pfSense kernel: ata3: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: atapci1: <intel pch="" sata300="" controller="">port 0xdcb0-0xdcb7,0xdc98-0xdc9b,0xdcb8-0xdcbf,0xdc9c-0xdc9f,0xdce0-0xdcef,0xdcf0-0xdcff irq 21 at device 31.5 on pci0
Nov 21 16:07:04 pfSense kernel: atapci1: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: ata4: <ata 0="" channel="">on atapci1
Nov 21 16:07:04 pfSense kernel: ata4: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: ata5: <ata 1="" channel="">on atapci1
Nov 21 16:07:04 pfSense kernel: ata5: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: atrtc0: <at realtime="" clock="">port 0x70-0x7f irq 8 on acpi0
Nov 21 16:07:04 pfSense kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Nov 21 16:07:04 pfSense kernel: uart0: [FILTER]
Nov 21 16:07:04 pfSense kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Nov 21 16:07:04 pfSense kernel: uart1: [FILTER]
Nov 21 16:07:04 pfSense kernel: orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xec000-0xeffff on isa0
Nov 21 16:07:04 pfSense kernel: atkbd: unable to set the command byte.
Nov 21 16:07:04 pfSense kernel: sc0: <system console="">at flags 0x100 on isa0
Nov 21 16:07:04 pfSense kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 21 16:07:04 pfSense kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 21 16:07:04 pfSense kernel: atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
Nov 21 16:07:04 pfSense kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
Nov 21 16:07:04 pfSense kernel: kbd0 at atkbd0
Nov 21 16:07:04 pfSense kernel: atkbd0: [GIANT-LOCKED]
Nov 21 16:07:04 pfSense kernel: atkbd0: [ITHREAD]
Nov 21 16:07:04 pfSense kernel: psm0: unable to set the command byte.
Nov 21 16:07:04 pfSense kernel: ppc0: cannot reserve I/O port range
Nov 21 16:07:04 pfSense kernel: est0: <enhanced speedstep="" frequency="" control="">on cpu0
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est0 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
Nov 21 16:07:04 pfSense kernel: est1: <enhanced speedstep="" frequency="" control="">on cpu1
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est1 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
Nov 21 16:07:04 pfSense kernel: est2: <enhanced speedstep="" frequency="" control="">on cpu2
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est2 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
Nov 21 16:07:04 pfSense kernel: est3: <enhanced speedstep="" frequency="" control="">on cpu3
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est3 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
Nov 21 16:07:04 pfSense kernel: est4: <enhanced speedstep="" frequency="" control="">on cpu4
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est4 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc4: <cpu frequency="" thermal="" control="">on cpu4
Nov 21 16:07:04 pfSense kernel: est5: <enhanced speedstep="" frequency="" control="">on cpu5
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est5 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc5: <cpu frequency="" thermal="" control="">on cpu5
Nov 21 16:07:04 pfSense kernel: est6: <enhanced speedstep="" frequency="" control="">on cpu6
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est6 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc6: <cpu frequency="" thermal="" control="">on cpu6
Nov 21 16:07:04 pfSense kernel: est7: <enhanced speedstep="" frequency="" control="">on cpu7
Nov 21 16:07:04 pfSense kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 21 16:07:04 pfSense kernel: est: cpu_vendor GenuineIntel, msr e
Nov 21 16:07:04 pfSense kernel: device_attach: est7 attach returned 6
Nov 21 16:07:04 pfSense kernel: p4tcc7: <cpu frequency="" thermal="" control="">on cpu7
Nov 21 16:07:04 pfSense kernel: Timecounters tick every 1.000 msec
Nov 21 16:07:04 pfSense kernel: IPsec: Initialized Security Association Processing.
Nov 21 16:07:04 pfSense kernel: usbus0: 480Mbps High Speed USB v2.0
Nov 21 16:07:04 pfSense kernel: usbus1: 480Mbps High Speed USB v2.0
Nov 21 16:07:04 pfSense kernel: ad4: 152587MB <wdc wd1602abks-18n8a0="" 02.03b05="">at ata2-master UDMA100 SATA 3Gb/s
Nov 21 16:07:04 pfSense kernel: ugen0.1: <intel>at usbus0
Nov 21 16:07:04 pfSense kernel: uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
Nov 21 16:07:04 pfSense kernel: ugen1.1: <intel>at usbus1
Nov 21 16:07:04 pfSense kernel: uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: ad6: 152587MB <wdc wd1602abks-18n8a0="" 02.03b05="">at ata3-master UDMA100 SATA 3Gb/s
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #1 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #4 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #3 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #7 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #5 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #2 Launched!
Nov 21 16:07:04 pfSense kernel: SMP: AP CPU #6 Launched!
Nov 21 16:07:04 pfSense kernel: GEOM_MIRROR: Device mirror/pfSenseMirror launched (2/2).
Nov 21 16:07:04 pfSense kernel: Root mount waiting for: usbus1 usbus0
Nov 21 16:07:04 pfSense kernel: uhub0: 2 ports with 2 removable, self powered
Nov 21 16:07:04 pfSense kernel: uhub1: 2 ports with 2 removable, self powered
Nov 21 16:07:04 pfSense kernel: ugen0.2: <vendor 0x8087="">at usbus0
Nov 21 16:07:04 pfSense kernel: uhub2: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
Nov 21 16:07:04 pfSense kernel: ugen1.2: <vendor 0x8087="">at usbus1
Nov 21 16:07:04 pfSense kernel: uhub3: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: Root mount waiting for: usbus1 usbus0
Nov 21 16:07:04 pfSense kernel: uhub2: 6 ports with 6 removable, self powered
Nov 21 16:07:04 pfSense kernel: uhub3: 8 ports with 8 removable, self powered
Nov 21 16:07:04 pfSense kernel: Root mount waiting for: usbus1 usbus0
Nov 21 16:07:04 pfSense kernel: ugen0.3: <vendor 0x0424="">at usbus0
Nov 21 16:07:04 pfSense kernel: uhub4: <vendor 3="" 9="" 0x0424="" product="" 0x2514,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
Nov 21 16:07:04 pfSense kernel: ugen1.3: <vendor 0x0557="">at usbus1
Nov 21 16:07:04 pfSense kernel: uhub5: <vendor 3="" 9="" 0x0557="" product="" 0x8021,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: uhub4: 4 ports with 4 removable, self powered
Nov 21 16:07:04 pfSense kernel: uhub5: 4 ports with 4 removable, self powered
Nov 21 16:07:04 pfSense kernel: ugen1.4: <aten international="" co.="" ltd="">at usbus1
Nov 21 16:07:04 pfSense kernel: ukbd0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: kbd2 at ukbd0
Nov 21 16:07:04 pfSense kernel: Root mount waiting for: usbus1
Nov 21 16:07:04 pfSense kernel: uhid0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: ums0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 21 16:07:04 pfSense kernel: ums0: 5 buttons and [XYZ] coordinates ID=0
Nov 21 16:07:04 pfSense kernel: ugen1.5: <dell>at usbus1
Nov 21 16:07:04 pfSense kernel: ukbd1: <ep1 interrupt="">on usbus1
Nov 21 16:07:04 pfSense kernel: kbd3 at ukbd1
Nov 21 16:07:04 pfSense kernel: Trying to mount root from ufs:/dev/mirror/pfSenseMirrors1a
Nov 21 16:07:04 pfSense kernel: pflog0: promiscuous mode enabled
Nov 21 16:07:04 pfSense apinger: Exiting on signal 15.
Nov 21 16:07:04 pfSense apinger: Starting Alarm Pinger, apinger(32626)
Nov 21 16:07:05 pfSense check_reload_status: Linkup starting igb1
Nov 21 16:07:05 pfSense kernel: igb1: link state changed to UP
Nov 21 16:07:05 pfSense php: : ROUTING: change default route to XXX.XXX.XXX.XXX
Nov 21 16:07:06 pfSense dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Nov 21 16:07:06 pfSense dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Nov 21 16:07:06 pfSense dhcpd: All rights reserved.
Nov 21 16:07:06 pfSense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 21 16:07:06 pfSense dnsmasq[46970]: started, version 2.55 cachesize 10000
Nov 21 16:07:06 pfSense dnsmasq[46970]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Nov 21 16:07:06 pfSense dnsmasq[46970]: reading /etc/resolv.conf
Nov 21 16:07:06 pfSense dnsmasq[46970]: using nameserver XXX.XXX.XXX.XXX#53
Nov 21 16:07:06 pfSense dnsmasq[46970]: using nameserver XXX.XXX.XXX.XXX#53
Nov 21 16:07:06 pfSense dnsmasq[46970]: using nameserver XXX.XXX.XXX.XXX#53
Nov 21 16:07:06 pfSense dnsmasq[46970]: using nameserver XXX.XXX.XXX.XXX#53
Nov 21 16:07:06 pfSense check_reload_status: updating all dyndns
Nov 21 16:07:06 pfSense dnsmasq[46970]: read /etc/hosts - 2 addresses
Nov 21 16:07:06 pfSense check_reload_status: Linkup starting igb3
Nov 21 16:07:06 pfSense kernel: igb3: link state changed to UP
Nov 21 16:07:10 pfSense php: : Creating rrd update script
Nov 21 16:07:10 pfSense php: : Resyncing configuration for all packages.
Nov 21 16:07:12 pfSense login: login on ttyv0 as root
Nov 21 16:07:12 pfSense sshlockout[25175]: sshlockout v2.0 starting up
Nov 21 16:07:12 pfSense sshlockout[25175]: sshlockout v2.0 starting up
Nov 21 16:12:09 pfSense sshd[57535]: error: PAM: authentication error for root from 172.20.3.20
Nov 21 16:12:09 pfSense sshd[57535]: error: PAM: authentication error for root from 172.20.3.20
Nov 21 16:12:15 pfSense sshd[57535]: error: PAM: authentication error for root from 172.20.3.20
Nov 21 16:12:17 pfSense sshd[57535]: Accepted keyboard-interactive/pam for root from 172.20.3.20 port 35108 ssh2</ep1></dell></aten></aten></aten></aten></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></wdc></intel></intel></intel></intel></wdc></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></at></ata></ata></intel></ata></ata></intel></isa></pci-isa></vga-compatible></acpi></acpi></intel></intel></bcm5709c></mii></broadcom></bcm5709c></mii></broadcom></acpi></acpi></acpi></acpi></intel></intel></atheros></acpi></acpi></intel(r)></intel(r)></pci></pci-pci></intel(r)></intel(r)></pci></pci-pci></pci></pci-pci></acpi></acpi></acpi></acpi></high></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></dell></software></version></dell ></lahf></syscall,nx,rdtscp,lm></sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt></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>

                      @wallabybob:

                      The referenced page says The problem is mbuf resources, the driver is autoconfiguring the number of queues based on the number of cores, on newer systems with lots of them this is outstripping the mbuf resource pool.

                      If you need to use more than the two interfaces a temporary workaround might be to use the uniprocessor kernel to test to see how many more interfaces you can get operational. I'm not familiar with the CPU(s) in your system so I don't know if this is relevant: FreeBSD used to (still does?) have a mechanism to disable hyperthreading, thus reducing the number of operational CPU cores. Either way you could try reducing the number of cores seen by the OS to see if that helps reduce the resource demands so you can get more interfaces operational.

                      OK, I'm currently running the uniprocessor kernel (see above) but I still see 8 logical CPUS.

                      This didn't work:

                      
[2.0-BETA4][root@pfSense.localdomain]/root(2): sysctl machdep.hlt_logical_cpus=1
sysctl: unknown oid 'machdep.hlt_logical_cpus'

                      @wallabybob:

                      To make the suggested change would probably involve setting up a pfSense build environment and building your own kernel or you might be able to persuade the pfSense developers to

                      • make the suggested change or

                      • add a sysctl to the igb driver to allow the num_queues variable to be changed at boot time or

                      • revert to the igb driver from FreeBSD 8.1 RELEASE

                      1: not sure about that, who do I contact? Can I open a ticket? I'm afraid this is getting increasingly lost in an irrelevant thread…
                      2: would be great!
                      3: unfortunately, the igb module is compiled in the kernel.

                      ifconfig with uniprocessor kernel (igb0,1 and 3 running as expected). I'll reboot the system a couple of times to see if the fix is holding...

                      [2.0-BETA4][root@pfSense.localdomain]/root(2): ifconfig
igb0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum>ether 00:1b:21:XX:XX:XX
	inet6 fe80::21b:21ff:feXX:XXXX%igb0 prefixlen 64 scopeid 0x1 
	inet XXX.XXX.XXX.XXX netmask 0xffff0000 broadcast XXX.XXX.XXX.255
	nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
igb1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum>ether 00:1b:21:6c:3e:19
	inet 172.20.1.1 netmask 0xffffff00 broadcast 172.20.1.255
	inet6 fe80::21b:21ff:fe6c:3e19%igb1 prefixlen 64 scopeid 0x2 
	nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
igb2: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
	options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 00:1b:21:6c:3e:1a
	media: Ethernet autoselect
	status: no carrier
igb3: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum>ether 00:1b:21:6c:3e:1b
	inet 172.20.3.1 netmask 0xffffff00 broadcast 172.20.3.255
	inet6 fe80::21b:21ff:fe6c:3e1b%igb3 prefixlen 64 scopeid 0x4 
	nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
ath0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 2290
	ether 00:26:5a:eb:9e:66
	media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
	status: no carrier
bce0: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
	options=c01bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso,linkstate>ether 84:2b:2b:0d:36:74
	media: Ethernet autoselect (none)
	status: no carrier
bce1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
	options=c01bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso,linkstate>ether 84:2b:2b:0d:36:75
	media: Ethernet autoselect (none)
	status: no carrier
lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
	options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 
	nd6 options=3 <performnud,accept_rtadv>pfsync0: flags=0<> metric 0 mtu 1460
	syncpeer: 224.0.0.240 maxupd: 128
pflog0: flags=100 <promisc>metric 0 mtu 33568
enc0: flags=0<> metric 0 mtu 1536</promisc></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso,linkstate></broadcast,simplex,multicast></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso,linkstate></broadcast,simplex,multicast></broadcast,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum></up,broadcast,running,simplex,multicast></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></broadcast,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum></up,broadcast,running,simplex,multicast>
                      1 Reply Last reply Reply Quote 0
                      • W
                        wallabybob
                        last edited by

                        Thanks for the dmesg output. Its useful to see what you are working with.

                        @John:

                        @wallabybob:

                        The referenced page says The problem is mbuf resources, the driver is autoconfiguring the number of queues based on the number of cores, on newer systems with lots of them this is outstripping the mbuf resource pool.

                        If you need to use more than the two interfaces a temporary workaround might be to use the uniprocessor kernel to test to see how many more interfaces you can get operational. I'm not familiar with the CPU(s) in your system so I don't know if this is relevant: FreeBSD used to (still does?) have a mechanism to disable hyperthreading, thus reducing the number of operational CPU cores. Either way you could try reducing the number of cores seen by the OS to see if that helps reduce the resource demands so you can get more interfaces operational.

                        OK, I'm currently running the uniprocessor kernel (see above) but I still see 8 logical CPUS.

                        This didn't work:

                        
[2.0-BETA4][root@pfSense.localdomain]/root(2): sysctl machdep.hlt_logical_cpus=1
sysctl: unknown oid 'machdep.hlt_logical_cpus'

                        That wasn't the sysctl I was thinking of, though it was close. The problem here is that the CPUS are enumerated at boot time and it appears the problem is provoked by the driver attaching at boot time and hence using the boot time CPU count. Halting logical CPUs after boot won't change the boot time CPU count. I thought there was a sysctl (possibly undocumented outside the source code) to disable hyperthreading, causing the CPU enumeration code that runs at boot time to count only physical CPUs. If the BIOS allows it, perhaps you could try disabling hyperthreading there.

                        @wallabybob:

                        To make the suggested change would probably involve setting up a pfSense build environment and building your own kernel or you might be able to persuade the pfSense developers to

                        • make the suggested change or

                        • add a sysctl to the igb driver to allow the num_queues variable to be changed at boot time or

                        • revert to the igb driver from FreeBSD 8.1 RELEASE

                        1: not sure about that, who do I contact? Can I open a ticket? I'm afraid this is getting increasingly lost in an irrelevant thread…
                        2: would be great!
                        3: unfortunately, the igb module is compiled in the kernel.

                        Suggest you open a ticket and reference this thread and suggest these three options. pfSense builds it own kernel so it is possible to "mix and match" drivers and kernel source. I don't know how often pfSense sources are synchronised with FreeBSD sources. Maybe the problem is fixed in current FreeBSD sources. (I haven't looked).

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

                          There is a FreeBSD mechanism in both i386 and amd64 kernels to disable (disallow) hyperthreading. In /boot/loader.conf.local add the line

                          machdep.hyperthreading_allowed="0"

                          By default hyperthreading is allowed. Remove the line to restore hyperthreading.

                          After boot, the shell command # kenv will display the kernel environment variables. You can use this to check that your addition to /boot/loader.conf.local was processed as expcted.

                          1 Reply Last reply Reply Quote 0
                          • L
                            littlejohn
                            last edited by

                            thanks, I'll try this first thing tomorrow morning…

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

                              If hyperthreading is disabled you should see just 4 CPUs launched at startup.

                              1 Reply Last reply Reply Quote 0
                              • L
                                littlejohn
                                last edited by

                                @wallabybob:

                                If hyperthreading is disabled you should see just 4 CPUs launched at startup.

                                For reference, this is the /var/log/system.log with hyperthreading disabled as instructed. Although now with the uniprocessor kernel, all my interfaces are UP and RUNNING.

                                My loader.conf:

                                
kern.ipc.nmbclusters="655356"
machdep.hyperthreading_allowed="0"

                                I still got bitten by the old DWA-556 bug now that I put the WLAN card back in (http://forum.pfsense.org/index.php/topic,27258.0.html) but other than that, everything seems OK as of 2.0-BETA4 (amd64) built on Sat Nov 20 08:25:10 UTC 2010.

                                Thanks ever so much for your help, wallabybob!

                                
Nov 22 09:01:20 vpn syslogd: kernel boot file is /boot/kernel/kernel
Nov 22 09:01:20 vpn kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Nov 22 09:01:20 vpn kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 22 09:01:20 vpn kernel: The Regents of the University of California. All rights reserved.
Nov 22 09:01:20 vpn kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 22 09:01:20 vpn kernel: FreeBSD 8.1-RELEASE-p1 #1: Sat Nov 20 08:16:31 UTC 2010
Nov 22 09:01:20 vpn kernel: sullrich@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 amd64
Nov 22 09:01:20 vpn kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 22 09:01:20 vpn kernel: CPU: Intel(R) Xeon(R) CPU           L3426  @ 1.87GHz (1862.00-MHz K8-class CPU)
Nov 22 09:01:20 vpn kernel: Origin = "GenuineIntel"  Id = 0x106e5  Family = 6  Model = 1e  Stepping = 5
Nov 22 09:01:20 vpn kernel: 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>Nov 22 09:01:20 vpn kernel: Features2=0x98e3fd <sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt>Nov 22 09:01:20 vpn kernel: AMD Features=0x28100800 <syscall,nx,rdtscp,lm>Nov 22 09:01:20 vpn kernel: AMD Features2=0x1 <lahf>Nov 22 09:01:20 vpn kernel: TSC: P-state invariant
Nov 22 09:01:20 vpn kernel: real memory  = 2147483648 (2048 MB)
Nov 22 09:01:20 vpn kernel: avail memory = 2035855360 (1941 MB)
Nov 22 09:01:20 vpn kernel: ACPI APIC Table: <dell  pe_sc3 ="">Nov 22 09:01:20 vpn kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Nov 22 09:01:20 vpn kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
Nov 22 09:01:20 vpn kernel: cpu0 (BSP): APIC ID:  0
Nov 22 09:01:20 vpn kernel: cpu1 (AP): APIC ID:  1
Nov 22 09:01:20 vpn kernel: cpu2 (AP): APIC ID:  2
Nov 22 09:01:20 vpn kernel: cpu3 (AP): APIC ID:  3
Nov 22 09:01:20 vpn kernel: cpu4 (AP): APIC ID:  4
Nov 22 09:01:20 vpn kernel: cpu5 (AP): APIC ID:  5
Nov 22 09:01:20 vpn kernel: cpu6 (AP): APIC ID:  6
Nov 22 09:01:20 vpn kernel: cpu7 (AP): APIC ID:  7
Nov 22 09:01:20 vpn kernel: ioapic0 <version 2.0="">irqs 0-23 on motherboard
Nov 22 09:01:20 vpn kernel: wlan: mac acl policy registered
Nov 22 09:01:20 vpn kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 22 09:01:20 vpn kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 22 09:01:20 vpn kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff804608a0, 0) error 1
Nov 22 09:01:20 vpn kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 22 09:01:20 vpn kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 22 09:01:20 vpn kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80460940, 0) error 1
Nov 22 09:01:20 vpn kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
Nov 22 09:01:20 vpn kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
Nov 22 09:01:20 vpn kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806447d0, 0) error 1
Nov 22 09:01:20 vpn kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 22 09:01:20 vpn kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 22 09:01:20 vpn kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff804609e0, 0) error 1
Nov 22 09:01:20 vpn kernel: kbd1 at kbdmux0
Nov 22 09:01:20 vpn kernel: cryptosoft0: <software crypto="">on motherboard
Nov 22 09:01:20 vpn kernel: padlock0: No ACE support.
Nov 22 09:01:20 vpn kernel: acpi0: <dell pe_sc3="">on motherboard
Nov 22 09:01:20 vpn kernel: acpi0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: acpi0: Power Button (fixed)
Nov 22 09:01:20 vpn kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Nov 22 09:01:20 vpn kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
Nov 22 09:01:20 vpn kernel: cpu0: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu1: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu2: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu3: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu4: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu5: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu6: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: cpu7: <acpi cpu="">on acpi0
Nov 22 09:01:20 vpn kernel: acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
Nov 22 09:01:20 vpn kernel: Timecounter "HPET" frequency 14318180 Hz quality 900
Nov 22 09:01:20 vpn kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
Nov 22 09:01:20 vpn kernel: pci0: <acpi pci="" bus="">on pcib0
Nov 22 09:01:20 vpn kernel: pcib1: <acpi pci-pci="" bridge="">at device 3.0 on pci0
Nov 22 09:01:20 vpn kernel: pci4: <acpi pci="" bus="">on pcib1
Nov 22 09:01:20 vpn kernel: pcib2: <pci-pci bridge="">at device 0.0 on pci4
Nov 22 09:01:20 vpn kernel: pci5: <pci bus="">on pcib2
Nov 22 09:01:20 vpn kernel: pcib3: <pci-pci bridge="">at device 2.0 on pci5
Nov 22 09:01:20 vpn kernel: pci6: <pci bus="">on pcib3
Nov 22 09:01:20 vpn kernel: igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xfcc0-0xfcdf mem 0xddfc0000-0xddfdffff,0xde000000-0xde3fffff,0xddfb8000-0xddfbbfff irq 18 at device 0.0 on pci6
Nov 22 09:01:20 vpn kernel: igb0: Using MSIX interrupts with 9 vectors
Nov 22 09:01:20 vpn kernel: igb0: [ITHREAD]
Nov 22 09:01:20 vpn last message repeated 8 times
Nov 22 09:01:20 vpn kernel: igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xfce0-0xfcff mem 0xddfe0000-0xddffffff,0xde400000-0xde7fffff,0xddfbc000-0xddfbffff irq 19 at device 0.1 on pci6
Nov 22 09:01:20 vpn kernel: igb1: Using MSIX interrupts with 9 vectors
Nov 22 09:01:20 vpn kernel: igb1: [ITHREAD]
Nov 22 09:01:20 vpn last message repeated 8 times
Nov 22 09:01:20 vpn kernel: pcib4: <pci-pci bridge="">at device 4.0 on pci5
Nov 22 09:01:20 vpn kernel: pci7: <pci bus="">on pcib4
Nov 22 09:01:20 vpn kernel: igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xecc0-0xecdf mem 0xdd3c0000-0xdd3dffff,0xdd400000-0xdd7fffff,0xdd3b8000-0xdd3bbfff irq 16 at device 0.0 on pci7
Nov 22 09:01:20 vpn kernel: igb2: Using MSIX interrupts with 9 vectors
Nov 22 09:01:20 vpn kernel: igb2: [ITHREAD]
Nov 22 09:01:20 vpn last message repeated 8 times
Nov 22 09:01:20 vpn kernel: igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.0.4="">port 0xece0-0xecff mem 0xdd3e0000-0xdd3fffff,0xdd800000-0xddbfffff,0xdd3bc000-0xdd3bffff irq 17 at device 0.1 on pci7
Nov 22 09:01:20 vpn kernel: igb3: Using MSIX interrupts with 9 vectors
Nov 22 09:01:20 vpn kernel: igb3: [ITHREAD]
Nov 22 09:01:20 vpn last message repeated 8 times
Nov 22 09:01:20 vpn kernel: pcib5: <acpi pci-pci="" bridge="">at device 5.0 on pci0
Nov 22 09:01:20 vpn kernel: pci8: <acpi pci="" bus="">on pcib5
Nov 22 09:01:20 vpn kernel: ath0: <atheros 5416="">mem 0xde9f0000-0xde9fffff irq 16 at device 0.0 on pci8
Nov 22 09:01:20 vpn kernel: ath0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: ath0: AR5418 mac 12.10 RF2133 phy 8.1
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 8.0 (no driver attached)
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 8.1 (no driver attached)
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 8.2 (no driver attached)
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 8.3 (no driver attached)
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 16.0 (no driver attached)
Nov 22 09:01:20 vpn kernel: pci0: <base peripheral=""> at device 16.1 (no driver attached)
Nov 22 09:01:20 vpn kernel: ehci0: <intel pch="" usb="" 2.0="" controller="" usb-b="">mem 0xde8fc000-0xde8fc3ff irq 22 at device 26.0 on pci0
Nov 22 09:01:20 vpn kernel: ehci0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: usbus0: EHCI version 1.0
Nov 22 09:01:20 vpn kernel: usbus0: <intel pch="" usb="" 2.0="" controller="" usb-b="">on ehci0
Nov 22 09:01:20 vpn kernel: pcib6: <acpi pci-pci="" bridge="">at device 28.0 on pci0
Nov 22 09:01:20 vpn kernel: pci3: <acpi pci="" bus="">on pcib6
Nov 22 09:01:20 vpn kernel: pcib7: <acpi pci-pci="" bridge="">at device 28.4 on pci0
Nov 22 09:01:20 vpn kernel: pci2: <acpi pci="" bus="">on pcib7
Nov 22 09:01:20 vpn kernel: bce0: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xd8000000-0xd9ffffff irq 16 at device 0.0 on pci2
Nov 22 09:01:20 vpn kernel: miibus0: <mii bus="">on bce0
Nov 22 09:01:20 vpn kernel: brgphy0: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus0
Nov 22 09:01:20 vpn kernel: brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 22 09:01:20 vpn kernel: bce0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: bce0: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.2); Flags (MSI|MFW); MFW (NCSI 2.0.8)
Nov 22 09:01:20 vpn kernel: bce1: <broadcom netxtreme="" ii="" bcm5716="" 1000base-t="" (c0)="">mem 0xda000000-0xdbffffff irq 17 at device 0.1 on pci2
Nov 22 09:01:20 vpn kernel: miibus1: <mii bus="">on bce1
Nov 22 09:01:20 vpn kernel: brgphy1: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus1
Nov 22 09:01:20 vpn kernel: brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 22 09:01:20 vpn kernel: bce1: [ITHREAD]
Nov 22 09:01:20 vpn kernel: bce1: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.2); Flags (MSI|MFW); MFW (NCSI 2.0.8)
Nov 22 09:01:20 vpn kernel: ehci1: <intel pch="" usb="" 2.0="" controller="" usb-a="">mem 0xde8fe000-0xde8fe3ff irq 22 at device 29.0 on pci0
Nov 22 09:01:20 vpn kernel: ehci1: [ITHREAD]
Nov 22 09:01:20 vpn kernel: usbus1: EHCI version 1.0
Nov 22 09:01:20 vpn kernel: usbus1: <intel pch="" usb="" 2.0="" controller="" usb-a="">on ehci1
Nov 22 09:01:20 vpn kernel: pcib8: <acpi pci-pci="" bridge="">at device 30.0 on pci0
Nov 22 09:01:20 vpn kernel: pci1: <acpi pci="" bus="">on pcib8
Nov 22 09:01:20 vpn kernel: vgapci0: <vga-compatible display="">mem 0xd7800000-0xd7ffffff,0xdc7fc000-0xdc7fffff,0xdc800000-0xdcffffff irq 19 at device 3.0 on pci1
Nov 22 09:01:20 vpn kernel: isab0: <pci-isa bridge="">at device 31.0 on pci0
Nov 22 09:01:20 vpn kernel: isa0: <isa bus="">on isab0
Nov 22 09:01:20 vpn kernel: atapci0: <intel pch="" sata300="" controller="">port 0xdca0-0xdca7,0xdc90-0xdc93,0xdca8-0xdcaf,0xdc94-0xdc97,0xdcc0-0xdccf,0xdcd0-0xdcdf irq 20 at device 31.2 on pci0
Nov 22 09:01:20 vpn kernel: atapci0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: ata2: <ata 0="" channel="">on atapci0
Nov 22 09:01:20 vpn kernel: ata2: [ITHREAD]
Nov 22 09:01:20 vpn kernel: ata3: <ata 1="" channel="">on atapci0
Nov 22 09:01:20 vpn kernel: ata3: [ITHREAD]
Nov 22 09:01:20 vpn kernel: atapci1: <intel pch="" sata300="" controller="">port 0xdcb0-0xdcb7,0xdc98-0xdc9b,0xdcb8-0xdcbf,0xdc9c-0xdc9f,0xdce0-0xdcef,0xdcf0-0xdcff irq 21 at device 31.5 on pci0
Nov 22 09:01:20 vpn kernel: atapci1: [ITHREAD]
Nov 22 09:01:20 vpn kernel: ata4: <ata 0="" channel="">on atapci1
Nov 22 09:01:20 vpn kernel: ata4: [ITHREAD]
Nov 22 09:01:20 vpn kernel: ata5: <ata 1="" channel="">on atapci1
Nov 22 09:01:20 vpn kernel: ata5: [ITHREAD]
Nov 22 09:01:20 vpn kernel: atrtc0: <at realtime="" clock="">port 0x70-0x7f irq 8 on acpi0
Nov 22 09:01:20 vpn kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Nov 22 09:01:20 vpn kernel: uart0: [FILTER]
Nov 22 09:01:20 vpn kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Nov 22 09:01:20 vpn kernel: uart1: [FILTER]
Nov 22 09:01:20 vpn kernel: orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xec000-0xeffff on isa0
Nov 22 09:01:20 vpn kernel: atkbd: unable to set the command byte.
Nov 22 09:01:20 vpn kernel: sc0: <system console="">at flags 0x100 on isa0
Nov 22 09:01:20 vpn kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 22 09:01:20 vpn kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 22 09:01:20 vpn kernel: atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
Nov 22 09:01:20 vpn kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
Nov 22 09:01:20 vpn kernel: kbd0 at atkbd0
Nov 22 09:01:20 vpn kernel: atkbd0: [GIANT-LOCKED]
Nov 22 09:01:20 vpn kernel: atkbd0: [ITHREAD]
Nov 22 09:01:20 vpn kernel: psm0: unable to set the command byte.
Nov 22 09:01:20 vpn kernel: ppc0: cannot reserve I/O port range
Nov 22 09:01:20 vpn kernel: est0: <enhanced speedstep="" frequency="" control="">on cpu0
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est0 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
Nov 22 09:01:20 vpn kernel: est1: <enhanced speedstep="" frequency="" control="">on cpu1
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est1 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
Nov 22 09:01:20 vpn kernel: est2: <enhanced speedstep="" frequency="" control="">on cpu2
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est2 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc2: <cpu frequency="" thermal="" control="">on cpu2
Nov 22 09:01:20 vpn kernel: est3: <enhanced speedstep="" frequency="" control="">on cpu3
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est3 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc3: <cpu frequency="" thermal="" control="">on cpu3
Nov 22 09:01:20 vpn kernel: est4: <enhanced speedstep="" frequency="" control="">on cpu4
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est4 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc4: <cpu frequency="" thermal="" control="">on cpu4
Nov 22 09:01:20 vpn kernel: est5: <enhanced speedstep="" frequency="" control="">on cpu5
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est5 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc5: <cpu frequency="" thermal="" control="">on cpu5
Nov 22 09:01:20 vpn kernel: est6: <enhanced speedstep="" frequency="" control="">on cpu6
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est6 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc6: <cpu frequency="" thermal="" control="">on cpu6
Nov 22 09:01:20 vpn kernel: est7: <enhanced speedstep="" frequency="" control="">on cpu7
Nov 22 09:01:20 vpn kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 22 09:01:20 vpn kernel: est: cpu_vendor GenuineIntel, msr e
Nov 22 09:01:20 vpn kernel: device_attach: est7 attach returned 6
Nov 22 09:01:20 vpn kernel: p4tcc7: <cpu frequency="" thermal="" control="">on cpu7
Nov 22 09:01:20 vpn kernel: Timecounters tick every 1.000 msec
Nov 22 09:01:20 vpn kernel: IPsec: Initialized Security Association Processing.
Nov 22 09:01:20 vpn kernel: usbus0: 480Mbps High Speed USB v2.0
Nov 22 09:01:20 vpn kernel: usbus1: 480Mbps High Speed USB v2.0
Nov 22 09:01:20 vpn kernel: ad4: 152587MB <wdc wd1602abks-18n8a0="" 02.03b05="">at ata2-master UDMA100 SATA 3Gb/s
Nov 22 09:01:20 vpn kernel: ugen0.1: <intel>at usbus0
Nov 22 09:01:20 vpn kernel: uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
Nov 22 09:01:20 vpn kernel: ugen1.1: <intel>at usbus1
Nov 22 09:01:20 vpn kernel: uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: ad6: 152587MB <wdc wd1602abks-18n8a0="" 02.03b05="">at ata3-master UDMA100 SATA 3Gb/s
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #1 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #4 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #3 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #2 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #5 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #7 Launched!
Nov 22 09:01:20 vpn kernel: SMP: AP CPU #6 Launched!
Nov 22 09:01:20 vpn kernel: GEOM_MIRROR: Device mirror/pfSenseMirror launched (2/2).
Nov 22 09:01:20 vpn kernel: Root mount waiting for: usbus1 usbus0
Nov 22 09:01:20 vpn kernel: uhub0: 2 ports with 2 removable, self powered
Nov 22 09:01:20 vpn kernel: uhub1: 2 ports with 2 removable, self powered
Nov 22 09:01:20 vpn kernel: Root mount waiting for: usbus1 usbus0
Nov 22 09:01:20 vpn kernel: ugen0.2: <vendor 0x8087="">at usbus0
Nov 22 09:01:20 vpn kernel: uhub2: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
Nov 22 09:01:20 vpn kernel: ugen1.2: <vendor 0x8087="">at usbus1
Nov 22 09:01:20 vpn kernel: uhub3: <vendor 2="" 9="" 0x8087="" product="" 0x0020,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: Root mount waiting for: usbus1 usbus0
Nov 22 09:01:20 vpn kernel: uhub2: 6 ports with 6 removable, self powered
Nov 22 09:01:20 vpn kernel: uhub3: 8 ports with 8 removable, self powered
Nov 22 09:01:20 vpn kernel: Root mount waiting for: usbus1 usbus0
Nov 22 09:01:20 vpn kernel: ugen0.3: <vendor 0x0424="">at usbus0
Nov 22 09:01:20 vpn kernel: uhub4: <vendor 3="" 9="" 0x0424="" product="" 0x2514,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
Nov 22 09:01:20 vpn kernel: ugen1.3: <vendor 0x0557="">at usbus1
Nov 22 09:01:20 vpn kernel: uhub5: <vendor 3="" 9="" 0x0557="" product="" 0x8021,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: uhub4: 4 ports with 4 removable, self powered
Nov 22 09:01:20 vpn kernel: uhub5: 4 ports with 4 removable, self powered
Nov 22 09:01:20 vpn kernel: ugen1.4: <aten international="" co.="" ltd="">at usbus1
Nov 22 09:01:20 vpn kernel: ukbd0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: Root mount waiting for: usbus1
Nov 22 09:01:20 vpn kernel: kbd2 at ukbd0
Nov 22 09:01:20 vpn kernel: uhid0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: ums0: <aten 0="" 4="" international="" co.="" ltd="" cl5708="" v1.0.098,="" class="" 0,="" rev="" 1.10="" 1.00,="" addr="">on usbus1
Nov 22 09:01:20 vpn kernel: ums0: 5 buttons and [XYZ] coordinates ID=0
Nov 22 09:01:20 vpn kernel: ugen1.5: <dell>at usbus1
Nov 22 09:01:20 vpn kernel: ukbd1: <ep1 interrupt="">on usbus1
Nov 22 09:01:20 vpn kernel: kbd3 at ukbd1
Nov 22 09:01:20 vpn kernel: Trying to mount root from ufs:/dev/mirror/pfSenseMirrors1a
Nov 22 09:01:20 vpn kernel: pflog0: promiscuous mode enabled
Nov 22 09:01:20 vpn php: : The command '/usr/local/sbin/relayd -f /var/etc/relayd.conf' returned exit code '1', the output was '/var/etc/relayd.conf:3: syntax error no redirections, nothing to do' 
Nov 22 09:01:20 vpn apinger: Exiting on signal 15.
Nov 22 09:01:20 vpn apinger: Starting Alarm Pinger, apinger(44562)
Nov 22 09:01:21 vpn check_reload_status: Linkup starting igb3
Nov 22 09:01:21 vpn kernel: igb3: link state changed to UP
Nov 22 09:01:22 vpn php: : ROUTING: change default route to XXX.XXX.XXX.XXX
Nov 22 09:01:22 vpn dhcpleases: Could not deliver signal HUP to process because its pidfile does not exist, No such file or directory.
Nov 22 09:01:22 vpn dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Nov 22 09:01:22 vpn dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Nov 22 09:01:22 vpn dhcpd: All rights reserved.
Nov 22 09:01:22 vpn dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 22 09:01:22 vpn dnsmasq[61583]: started, version 2.55 cachesize 10000
Nov 22 09:01:22 vpn dnsmasq[61583]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Nov 22 09:01:22 vpn dnsmasq[61583]: reading /etc/resolv.conf
Nov 22 09:01:22 vpn dnsmasq[61583]: using nameserver XXX.XXX.XXX.XXX#53
Nov 22 09:01:22 vpn dnsmasq[61583]: using nameserver XXX.XXX.XXX.XXX#53
Nov 22 09:01:22 vpn dnsmasq[61583]: using nameserver XXX.XXX.XXX.XXX#53
Nov 22 09:01:22 vpn dnsmasq[61583]: using nameserver XXX.XXX.XXX.XXX#53
Nov 22 09:01:22 vpn dnsmasq[61583]: read /etc/hosts - 8 addresses
Nov 22 09:01:22 vpn last message repeated 3 times
Nov 22 09:01:22 vpn check_reload_status: updating all dyndns
Nov 22 09:01:26 vpn php: : Creating rrd update script
Nov 22 09:01:27 vpn php: : Resyncing configuration for all packages.
Nov 22 09:01:22 vpn dnsmasq[61583]: read /etc/hosts - 8 addresses
Nov 22 09:01:28 vpn login: login on ttyv0 as root
Nov 22 09:01:28 vpn sshlockout[13847]: sshlockout v2.0 starting up
Nov 22 09:01:28 vpn sshlockout[13847]: sshlockout v2.0 starting up
Nov 22 09:02:17 vpn sshd[10249]: Accepted keyboard-interactive/pam for root from 172.20.3.20 port 36563 ssh2</ep1></dell></aten></aten></aten></aten></vendor></vendor></vendor></vendor></vendor></vendor></vendor></vendor></wdc></intel></intel></intel></intel></wdc></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></at></ata></ata></intel></ata></ata></intel></isa></pci-isa></vga-compatible></acpi></acpi></intel></intel></bcm5709c></mii></broadcom></bcm5709c></mii></broadcom></acpi></acpi></acpi></acpi></intel></intel></atheros></acpi></acpi></intel(r)></intel(r)></pci></pci-pci></intel(r)></intel(r)></pci></pci-pci></pci></pci-pci></acpi></acpi></acpi></acpi></high></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></dell></software></version></dell ></lahf></syscall,nx,rdtscp,lm></sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,popcnt></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>

                                Regards,
                                John

                                1 Reply Last reply Reply Quote 0
                                • I
                                  innosys
                                  last edited by

                                  Ran into the same problem with quad port cards using the igb driver.

                                  Opened a bug report in the bug tracker: http://redmine.pfsense.com/issues/1221

                                  Another bug, 560 ends up wiping the loader.conf settings after updates which ends up killing the box since the mbuf and hyperthreading settings get nuked.

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

                                    @innosys:

                                    Another bug, 560 ends up wiping the loader.conf settings after updates which ends up killing the box since the mbuf and hyperthreading settings get nuked.

                                    "Private" settings need to go into loader.conf.local which is preserved across upgrades. If you want more information search this forum.

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      tacfit
                                      last edited by

                                      We've not run into this problem yet, but we are also using IGB on a powerful multicore server, so I'd be interested to see a resolution on this.

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