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

    Watchguard XTM 5 Series

    Scheduled Pinned Locked Moved Hardware
    1.1k Posts 130 Posters 1.4m 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.
    • chpalmerC
      chpalmer
      last edited by

      @blaxx:

      The "issue" is that both of the firewalls have the same problem and they ran fine with Watchguard OS on them. I have a hard time believing that there should be faulty hardware on both of them but I can't be certain.

      I have a console cable I can plug in and connect with putty but I'm very new to pfsense and linux in general so I don't know what you want me to test.

      Do you have a command I should write when the error occurs?

      choose option 8 and type dmesg after a failure.

      When you say you can't reach the gui- are you using a host name or an IP address?

      I don't think your boxes are bad..  I think you have a switch or other device on you network going south. But some troubleshooting is in order.

      Triggering snowflakes one by one..
      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

      1 Reply Last reply Reply Quote 0
      • B
        blaxx
        last edited by

        @chpalmer:

        @blaxx:

        The "issue" is that both of the firewalls have the same problem and they ran fine with Watchguard OS on them. I have a hard time believing that there should be faulty hardware on both of them but I can't be certain.

        I have a console cable I can plug in and connect with putty but I'm very new to pfsense and linux in general so I don't know what you want me to test.

        Do you have a command I should write when the error occurs?

        choose option 8 and type dmesg after a failure.

        When you say you can't reach the gui- are you using a host name or an IP address?

        I don't think your boxes are bad..  I think you have a switch or other device on you network going south. But some troubleshooting is in order.

        Connecting through IP to the gui.

        I dont have any switches attached to the firewalls. One of them is just powered up with nothing connected to it and the other one has a DSL-line in WAN and one PC in LAN0.

        I will try dmesg and reply here next time it happens.

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

          @blaxx
          Yeah, if the console responds at all then it's probably not a hardware problem. Just hitting return there should re-draw the console menu. Something should be logged.

          @747Builder
          Do you see Speedstep working correctly on any of those?

          I have a feeling it could just be the CPU (E4500) I have here but it's the only one I've tested it with so….

          Steve

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

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              On the dashboard it will report the Current vs Max frequency, that's probably easiest. See screenshot.

              You can also see the current and available levels in the sysctls:

              [2.4.0-BETA][root@8860.stevew.lan]/root: sysctl dev.cpu.0
              dev.cpu.0.temperature: 32.0C
              dev.cpu.0.coretemp.throttle_log: 0
              dev.cpu.0.coretemp.tjmax: 98.0C
              dev.cpu.0.coretemp.resolution: 1
              dev.cpu.0.coretemp.delta: 66
              dev.cpu.0.cx_method: C1/hlt
              dev.cpu.0.cx_usage_counters: 2723221
              dev.cpu.0.cx_usage: 100.00% last 47776us
              dev.cpu.0.cx_lowest: C1
              dev.cpu.0.cx_supported: C1/1/0
              dev.cpu.0.freq_levels: 2400/8 2200/0 2000/0 1800/0 1600/0 1400/0 1200/0
              dev.cpu.0.freq: 1200
              dev.cpu.0.%parent: acpi0
              dev.cpu.0.%pnpinfo: _HID=none _UID=0
              dev.cpu.0.%location: handle=\_PR_.CPU0
              dev.cpu.0.%driver: cpu
              dev.cpu.0.%desc: ACPI CPU
              
              

              And you can see the est driver loader against the cpu cores:

              [2.4.0-BETA][root@8860.stevew.lan]/root: cat /var/log/dmesg.boot | grep est
              est0: <enhanced speedstep="" frequency="" control="">on cpu0
              est1: <enhanced speedstep="" frequency="" control="">on cpu1
              est2: <enhanced speedstep="" frequency="" control="">on cpu2
              est3: <enhanced speedstep="" frequency="" control="">on cpu3</enhanced></enhanced></enhanced></enhanced> 
              

              Steve

              Selection_277.png
              Selection_277.png_thumb

              1 Reply Last reply Reply Quote 0
              • S
                SONiQz
                last edited by

                Hi All,

                I have an XTM505 and an XTM330 which we've pulled from active service…. So now I have some new desk ornaments!

                Anyway, I've pulled the 505 apart and had aimed to see what pfSense can do for me. So I've thrown a new Kingston 4GB CF in with a 2GB image of "pfSense 2.3.4 NanoBSD" as I was hoping to run from the CF, however I seem to run into a somewhat inconsistent issue. If I reboot the device the CF seems to sometimes crap itself and I get dumped into a Single User Mode prompt (if it gets past POST) and errors when I try to remount the CF as R/W so then I need to reflash..... Hardly ideal.

                I do see errors like: "DMA limited to UDMA33, controller found non-ATA66 cable" when it does successfully boot, but other than that there's nothing out of the ordinary. I have dropped the original 1GB CF back in and that seems fine so I don't think there is a board issue. And the 4GB CF is new and seems to write and verify so I am a bit baffled as I wasn't really planning on dropping a HDD in it as I don't have a cradle spare.

                Has anyone else had similar issues or suggestions as to what may be causing the problem I'm all ears!

                Thanks in advance

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

                  I didn't think it was required on that board but you may need to disable UDMA for CF card if yours is particularly fussy:
                  https://doc.pfsense.org/index.php/Boot_Troubleshooting#pfSense_2.2_and_later

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • D
                    DeLorean
                    last edited by

                    @SONiQz:

                    Hi All,

                    I have an XTM505 and an XTM330 which we've pulled from active service…. So now I have some new desk ornaments!

                    Anyway, I've pulled the 505 apart and had aimed to see what pfSense can do for me. So I've thrown a new Kingston 4GB CF in with a 2GB image of "pfSense 2.3.4 NanoBSD" as I was hoping to run from the CF, however I seem to run into a somewhat inconsistent issue. If I reboot the device the CF seems to sometimes crap itself and I get dumped into a Single User Mode prompt (if it gets past POST) and errors when I try to remount the CF as R/W so then I need to reflash..... Hardly ideal.

                    I do see errors like: "DMA limited to UDMA33, controller found non-ATA66 cable" when it does successfully boot, but other than that there's nothing out of the ordinary. I have dropped the original 1GB CF back in and that seems fine so I don't think there is a board issue. And the 4GB CF is new and seems to write and verify so I am a bit baffled as I wasn't really planning on dropping a HDD in it as I don't have a cradle spare.

                    Has anyone else had similar issues or suggestions as to what may be causing the problem I'm all ears!

                    Thanks in advance

                    If you use the Kingston 4GB standard type, that's without doubt your cause of problems.
                    These cards are so slow that they cause all kinds of ATA errors.
                    Disabling UDMA will not help for this issue.
                    I have seen this behaviour the first time on a x750e , and there was UDMA disabled and still ATA errors.
                    Switching to another brand or use the 16Gb High Speed version of Kingston and your problem is vanished :-)

                    Grtz
                    DeLorean

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

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • B
                        Billyboy
                        last edited by

                        Hi all,
                        I have two XTM5 (505 and 515) with the BIOS:

                        Vendor: American Megatrends Inc.
                        Version: 080015
                        Release Date: 02/03/2010

                        and upgraded hardware on both:

                        CPU: Intel E5800 @ 3.2 Ghz
                        RAM: 2 GB
                        SSD: 60 GB

                        running on the latest pfsense 2.3.4-p1.

                        I have configured the boxes for HA failover through CARP and with MultiWAN.

                        While I was testing the failover, I recognized problem:

                        When I pull a cable out of any of the em ports, Pfsense needs more than 5 Minutes to change the interface to down (both in the GUI DASHBOARD as well as on the Interfaces status page). However the port LEDs are switched off imediatelly.

                        I found the following in the syslog:

                        Aug 24 16:24:35 php-fpm[55068]: /rc.dyndns.update: MONITOR: WAN5_1GW is down, omitting from routing group WAN_GWG_654_LB 199.7.83.42|192.168.245.101|WAN5_1GW|17.248ms|4.241ms|24%|down
                        Aug 24 16:31:24 kernel: em4: Watchdog timeout Queue[0]– resetting
                        Aug 24 16:31:24 kernel: Interface is RUNNING and ACTIVE
                        Aug 24 16:31:24 kernel: em4: TX Queue 0 ------
                        Aug 24 16:31:24 kernel: em4: hw tdh = 61, hw tdt = 21
                        Aug 24 16:31:24 kernel: em4: Tx Queue Status = -2147483648
                        Aug 24 16:31:24 kernel: em4: TX descriptors avail = 40
                        Aug 24 16:31:24 kernel: em4: Tx Descriptors avail failure = 39
                        Aug 24 16:31:24 kernel: em4: RX Queue 0 ------
                        Aug 24 16:31:24 kernel: em4: hw rdh = 518, hw rdt = 517
                        Aug 24 16:31:24 kernel: em4: RX discarded packets = 0
                        Aug 24 16:31:24 kernel: em4: RX Next to Check = 518
                        Aug 24 16:31:24 kernel: em4: RX Next to Refresh = 517
                        Aug 24 16:31:24 kernel: carp: demoted by 240 to 240 (interface down)
                        Aug 24 16:31:24 kernel: em4: link state changed to DOWN

                        On the first entry (16:24:35), the Gateway goes down because of the disconnected cable.
                        More than 6 Minutes later, at 16:31:24 the system changed the link state to down.

                        On the fxp0 port, everything works fine.

                        Anyone have an idea regarding what might be the problem?

                        Kind regards

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

                          Hmm, curious, I don't think I've ever seen that.

                          Do you see that happen with all the NICs or just em4? Both boxes behave like that?

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • B
                            Billyboy
                            last edited by

                            This happens to both boxes on all em Ports.  :(

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

                              Hmm, and you're actually pulling the cable from the port on the xtm5?

                              What does ifconfig show for that port during that time?

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • S
                                Smoothrunnings
                                last edited by

                                On the WatchGuard XTM 5 motherboard do any of the pin-outs and or sockets support a VGA connector?

                                I have been looking on Google but nothing I see points to anyone investigating if a VGA connector can be connected to the motherboard or not.

                                Thanks,

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

                                  It does have a VGA header, J9, on the rear left of the board. It's a 2mm pitch connector though like most of these boxes not the more common 0.1".

                                  I've never tried it myself.

                                  Steve

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

                                    Edit: See post below…

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

                                      I took antother dump using a Raspberry Pi which had same sha256, so I'm pretty sure is got the dump right. Next I downgraded my BIOS to the mod'ed one… it works :)

                                      I enabled PowerD, added the additional lines to the loader.conf file, added timecounter variable... but SpeedStep does not seem to work:

                                      "CPU supports enhanced SpeedStep, but it's not recognized", also sysctl shows no freq_levels.

                                      My CPU does support it (Pentium E5800). Has anyone got it working? Ís there anything that needs to be changed in BIOS? Would be happy to lower the power consumption this way. Powermeter meassures around 32-33W idle at the moment.

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        blaxx
                                        last edited by

                                        @blaxx:

                                        Hi !

                                        I don't know if this is a pfsense or XTM5 problem but I'll give it a try.

                                        I have two XTM5 (510 and 525) with original BIOS and hardware except for hard drives that I have installed latest pfsense 2.3.4-p1 on. I have never used pfsense before so I installed it on these firewalls to see if it works. No changes are made on the config after first boot.

                                        The problem is that after a couple of days both of the firewalls stops routing all traffic. Cant reach them from webgui and cant connect to internet at all anymore.
                                        The only solution I've found is to pull the plug. After that it works for a couple of days again.

                                        I read an old thread regarding a bug when using multicore cpu so I tried that fix by disabling all but one core but that didn't help.

                                        Anyone have an idea regarding what might be the problem?

                                        Kind regards

                                        Stellan

                                        So. I'm back now with the same problem again.
                                        Since last time I've switched CPU, reinstalled pfsense from a new flashcard. This time it worked for nearly 14 days. 10 of these days with DSL connected to WAN and 1 pc direct connect to LAN0. The last four days the FW was only connected to DSL and nothin on LAN.

                                        Today I connected a PC to LAN0 and no DHCP recieved. I can connect to console with consolecable trough Putty
                                        I can ping both WAN and LAN interface and even google dns (8.8.8.8) via consolecable.
                                        Can't reach webpages nor webinterface if I set static IP on PC.

                                        Can anyone give me some tips to trace this problem?

                                        Regards Stellan

                                        Dmesg shows this:

                                        [2.3.4-RELEASE][root@pfSense.JTT.local]/root: dmesg
                                        Copyright (c) 1992-2016 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 10.3-RELEASE-p19 #1 76a12c4e6(RELENG_2_3_4): Fri Jul 14 15:02:35 CDT 2017
                                            root@ce23-amd64-builder:/builder/pfsense-234/tmp/obj/builder/pfsense-234/tmp/FreeBSD-src/sys/pfSense amd64
                                        FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
                                        CPU: Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz (2327.54-MHz K8-class CPU)
                                          Origin="GenuineIntel"  Id=0x1067a  Family=0x6  Model=0x17  Stepping=10
                                          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=0xc08e39d <sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave,osxsave>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant, performance statistics
                                        real memory  = 2147483648 (2048 MB)
                                        avail memory = 2003542016 (1910 MB)
                                        Event timer "LAPIC" quality 400
                                        ACPI APIC Table: <042610 APIC1157>
                                        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:  1
                                         cpu2 (AP): APIC ID:  2
                                         cpu3 (AP): APIC ID:  3
                                        random: <software, yarrow="">initialized
                                        ioapic0 <version 2.0="">irqs 0-23 on motherboard
                                        wlan: mac acl policy registered
                                        ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff806209f0, 0) error 1
                                        ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80620aa0, 0) error 1
                                        ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80620b50, 0) error 1
                                        iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80647cf0, 0) error 1
                                        iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80647da0, 0) error 1
                                        iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80647e50, 0) error 1
                                        netmap: loaded module
                                        kbd1 at kbdmux0
                                        cryptosoft0: <software crypto="">on motherboard
                                        padlock0: No ACE support.
                                        acpi0: <042610 RSDT1157> on motherboard
                                        acpi0: Power Button (fixed)
                                        cpu0: <acpi cpu="">on acpi0
                                        cpu1: <acpi cpu="">on acpi0
                                        cpu2: <acpi cpu="">on acpi0
                                        cpu3: <acpi cpu="">on acpi0
                                        attimer0: <at timer="">port 0x40-0x43 irq 0 on acpi0
                                        Timecounter "i8254" frequency 1193182 Hz quality 0
                                        Event timer "i8254" frequency 1193182 Hz quality 100
                                        atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
                                        Event timer "RTC" frequency 32768 Hz quality 0
                                        Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
                                        acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
                                        pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                                        pci0: <acpi pci="" bus="">on pcib0
                                        vgapci0: <vga-compatible display="">port 0x6800-0x6807 mem 0xfe000000-0xfe3fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
                                        agp0: <intel g41="" svga="" controller="">on vgapci0
                                        agp0: aperture size is 256M, detected 32764k stolen memory
                                        vgapci0: Boot video device
                                        pcib1: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
                                        pci2: <acpi pci="" bus="">on pcib1
                                        em0: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0x9c00-0x9c1f mem 0xfe6e0000-0xfe6fffff,0xfe6dc000-0xfe6dffff irq 16 at device 0.0 on pci2
                                        em0: Using MSIX interrupts with 3 vectors
                                        em0: Ethernet address: 00:90:7f:9f:5f:6b
                                        em0: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib2: <acpi pci-pci="" bridge="">irq 17 at device 28.1 on pci0
                                        pci3: <acpi pci="" bus="">on pcib2
                                        em1: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xac00-0xac1f mem 0xfe7e0000-0xfe7fffff,0xfe7dc000-0xfe7dffff irq 17 at device 0.0 on pci3
                                        em1: Using MSIX interrupts with 3 vectors
                                        em1: Ethernet address: 00:90:7f:9f:5f:6c
                                        em1: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib3: <acpi pci-pci="" bridge="">irq 18 at device 28.2 on pci0
                                        pci4: <acpi pci="" bus="">on pcib3
                                        em2: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 18 at device 0.0 on pci4
                                        em2: Using MSIX interrupts with 3 vectors
                                        em2: Ethernet address: 00:90:7f:9f:5f:6d
                                        em2: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib4: <acpi pci-pci="" bridge="">irq 19 at device 28.3 on pci0
                                        pci5: <acpi pci="" bus="">on pcib4
                                        em3: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 19 at device 0.0 on pci5
                                        em3: Using MSIX interrupts with 3 vectors
                                        em3: Ethernet address: 00:90:7f:9f:5f:6e
                                        em3: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib5: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
                                        pci6: <acpi pci="" bus="">on pcib5
                                        em4: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 16 at device 0.0 on pci6
                                        em4: Using MSIX interrupts with 3 vectors
                                        em4: Ethernet address: 00:90:7f:9f:5f:6f
                                        em4: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib6: <acpi pci-pci="" bridge="">irq 17 at device 28.5 on pci0
                                        pci7: <acpi pci="" bus="">on pcib6
                                        em5: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff,0xfebdc000-0xfebdffff irq 17 at device 0.0 on pci7
                                        em5: Using MSIX interrupts with 3 vectors
                                        em5: Ethernet address: 00:90:7f:9f:5f:70
                                        em5: netmap queues/slots: TX 1/1024, RX 1/1024
                                        uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a="">port 0x7080-0x709f irq 23 at device 29.0 on pci0
                                        usbus0 on uhci0
                                        uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b="">port 0x7000-0x701f irq 19 at device 29.1 on pci0
                                        usbus1 on uhci1
                                        uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c="">port 0x6c00-0x6c1f irq 18 at device 29.2 on pci0
                                        usbus2 on uhci2
                                        uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d="">port 0x6880-0x689f irq 16 at device 29.3 on pci0
                                        usbus3 on uhci3
                                        ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xfe4ff800-0xfe4ffbff irq 23 at device 29.7 on pci0
                                        usbus4: EHCI version 1.0
                                        usbus4 on ehci0
                                        pcib7: <acpi pci-pci="" bridge="">at device 30.0 on pci0
                                        pci1: <acpi pci="" bus="">on pcib7
                                        fxp0: <intel 10="" 100="" 82801gb="" (ich7)="" ethernet="">port 0x8c00-0x8c3f mem 0xfe5ff000-0xfe5fffff irq 20 at device 8.0 on pci1
                                        miibus0: <mii bus="">on fxp0
                                        inphy0: <i82562et 10="" 100="" media="" interface="">PHY 1 on miibus0
                                        inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
                                        fxp0: Ethernet address: 00:90:7f:9f:5f:6a
                                        isab0: <pci-isa bridge="">at device 31.0 on pci0
                                        isa0: <isa bus="">on isab0
                                        atapci0: <intel ich7="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
                                        ata0: <ata channel="">at channel 0 on atapci0
                                        atapci1: <intel ich7="" sata300="" controller="">port 0x7c00-0x7c07,0x7880-0x7883,0x7800-0x7807,0x7480-0x7483,0x7400-0x740f mem 0xfe4ffc00-0xfe4fffff irq 19 at device 31.2 on pci0
                                        ata2: <ata channel="">at channel 0 on atapci1
                                        ata3: <ata channel="">at channel 1 on atapci1
                                        acpi_button0: <power button="">on acpi0
                                        uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
                                        uart0: console (115200,n,8,1)
                                        uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
                                        ppc0: <parallel port="">port 0x378-0x37f irq 7 on acpi0
                                        ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
                                        ppbus0: <parallel port="" bus="">on ppc0
                                        lpt0: <printer>on ppbus0
                                        lpt0: Interrupt-driven port
                                        ppi0: <parallel i="" o="">on ppbus0
                                        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]
                                        est0: <enhanced speedstep="" frequency="" control="">on cpu0
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est0 attach returned 6
                                        est1: <enhanced speedstep="" frequency="" control="">on cpu1
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est1 attach returned 6
                                        est2: <enhanced speedstep="" frequency="" control="">on cpu2
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est2 attach returned 6
                                        est3: <enhanced speedstep="" frequency="" control="">on cpu3
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est3 attach returned 6
                                        Timecounters tick every 1.000 msec
                                        random: unblocking device.
                                        usbus0: 12Mbps Full Speed USB v1.0
                                        usbus1: 12Mbps Full Speed USB v1.0
                                        usbus2: 12Mbps Full Speed USB v1.0
                                        usbus3: 12Mbps Full Speed USB v1.0
                                        ugen0.1: <intel>at usbus0
                                        uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
                                        ugen1.1: <intel>at usbus1
                                        uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
                                        ugen2.1: <intel>at usbus2
                                        uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
                                        ugen3.1: <intel>at usbus3
                                        uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
                                        usbus4: 480Mbps High Speed USB v2.0
                                        ugen4.1: <intel>at usbus4
                                        uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
                                        uhub0: 2 ports with 2 removable, self powered
                                        uhub1: 2 ports with 2 removable, self powered
                                        uhub2: 2 ports with 2 removable, self powered
                                        uhub3: 2 ports with 2 removable, self powered
                                        uhub4: 8 ports with 8 removable, self powered
                                        ada0 at ata2 bus 0 scbus1 target 0 lun 0
                                        ada0: <samsung hm250ji="" hs100-10="">ATA8-ACS SATA 1.x device
                                        ada0: Serial Number S15YJD0PB08244
                                        ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
                                        ada0: 238475MB (488397168 512 byte sectors)
                                        ada0: Previously was known as ad4
                                        SMP: AP CPU #3 Launched!
                                        SMP: AP CPU #1 Launched!
                                        SMP: AP CPU #2 Launched!
                                        Timecounter "TSC-low" frequency 1163771717 Hz quality 1000
                                        Trying to mount root from ufs:/dev/ufsid/5996b7217d4aca1d [rw]...
                                        coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
                                        est0: <enhanced speedstep="" frequency="" control="">on cpu0
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est0 attach returned 6
                                        coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1
                                        est1: <enhanced speedstep="" frequency="" control="">on cpu1
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est1 attach returned 6
                                        coretemp2: <cpu on-die="" thermal="" sensors="">on cpu2
                                        est2: <enhanced speedstep="" frequency="" control="">on cpu2
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est2 attach returned 6
                                        coretemp3: <cpu on-die="" thermal="" sensors="">on cpu3
                                        est3: <enhanced speedstep="" frequency="" control="">on cpu3
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est3 attach returned 6
                                        em0: link state changed to UP
                                        pflog0: promiscuous mode enabled
                                        em1: link state changed to UP
                                        fxp0: link state changed to DOWN
                                        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...4 0 0 done
                                        All buffers synced.
                                        Copyright (c) 1992-2016 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 10.3-RELEASE-p19 #1 76a12c4e6(RELENG_2_3_4): Fri Jul 14 15:02:35 CDT 2017
                                            root@ce23-amd64-builder:/builder/pfsense-234/tmp/obj/builder/pfsense-234/tmp/FreeBSD-src/sys/pfSense amd64
                                        FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
                                        CPU: Intel(R) Core(TM)2 Quad CPU    Q8200  @ 2.33GHz (2327.55-MHz K8-class CPU)
                                          Origin="GenuineIntel"  Id=0x1067a  Family=0x6  Model=0x17  Stepping=10
                                          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=0xc08e39d <sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave,osxsave>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant, performance statistics
                                        real memory  = 2147483648 (2048 MB)
                                        avail memory = 2003542016 (1910 MB)
                                        Event timer "LAPIC" quality 400
                                        ACPI APIC Table: <042610 APIC1157>
                                        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:  1
                                         cpu2 (AP): APIC ID:  2
                                         cpu3 (AP): APIC ID:  3
                                        random: <software, yarrow="">initialized
                                        ioapic0 <version 2.0="">irqs 0-23 on motherboard
                                        wlan: mac acl policy registered
                                        ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff806209f0, 0) error 1
                                        ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80620aa0, 0) error 1
                                        ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                                        ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80620b50, 0) error 1
                                        iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80647cf0, 0) error 1
                                        iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80647da0, 0) error 1
                                        iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                                        iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                                        module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80647e50, 0) error 1
                                        netmap: loaded module
                                        kbd1 at kbdmux0
                                        cryptosoft0: <software crypto="">on motherboard
                                        padlock0: No ACE support.
                                        acpi0: <042610 RSDT1157> on motherboard
                                        acpi0: Power Button (fixed)
                                        cpu0: <acpi cpu="">on acpi0
                                        cpu1: <acpi cpu="">on acpi0
                                        cpu2: <acpi cpu="">on acpi0
                                        cpu3: <acpi cpu="">on acpi0
                                        attimer0: <at timer="">port 0x40-0x43 irq 0 on acpi0
                                        Timecounter "i8254" frequency 1193182 Hz quality 0
                                        Event timer "i8254" frequency 1193182 Hz quality 100
                                        atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
                                        Event timer "RTC" frequency 32768 Hz quality 0
                                        Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
                                        acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
                                        pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                                        pci0: <acpi pci="" bus="">on pcib0
                                        vgapci0: <vga-compatible display="">port 0x6800-0x6807 mem 0xfe000000-0xfe3fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
                                        agp0: <intel g41="" svga="" controller="">on vgapci0
                                        agp0: aperture size is 256M, detected 32764k stolen memory
                                        vgapci0: Boot video device
                                        pcib1: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
                                        pci2: <acpi pci="" bus="">on pcib1
                                        em0: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0x9c00-0x9c1f mem 0xfe6e0000-0xfe6fffff,0xfe6dc000-0xfe6dffff irq 16 at device 0.0 on pci2
                                        em0: Using MSIX interrupts with 3 vectors
                                        em0: Ethernet address: 00:90:7f:9f:5f:6b
                                        em0: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib2: <acpi pci-pci="" bridge="">irq 17 at device 28.1 on pci0
                                        pci3: <acpi pci="" bus="">on pcib2
                                        em1: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xac00-0xac1f mem 0xfe7e0000-0xfe7fffff,0xfe7dc000-0xfe7dffff irq 17 at device 0.0 on pci3
                                        em1: Using MSIX interrupts with 3 vectors
                                        em1: Ethernet address: 00:90:7f:9f:5f:6c
                                        em1: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib3: <acpi pci-pci="" bridge="">irq 18 at device 28.2 on pci0
                                        pci4: <acpi pci="" bus="">on pcib3
                                        em2: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 18 at device 0.0 on pci4
                                        em2: Using MSIX interrupts with 3 vectors
                                        em2: Ethernet address: 00:90:7f:9f:5f:6d
                                        em2: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib4: <acpi pci-pci="" bridge="">irq 19 at device 28.3 on pci0
                                        pci5: <acpi pci="" bus="">on pcib4
                                        em3: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 19 at device 0.0 on pci5
                                        em3: Using MSIX interrupts with 3 vectors
                                        em3: Ethernet address: 00:90:7f:9f:5f:6e
                                        em3: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib5: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
                                        pci6: <acpi pci="" bus="">on pcib5
                                        em4: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 16 at device 0.0 on pci6
                                        em4: Using MSIX interrupts with 3 vectors
                                        em4: Ethernet address: 00:90:7f:9f:5f:6f
                                        em4: netmap queues/slots: TX 1/1024, RX 1/1024
                                        pcib6: <acpi pci-pci="" bridge="">irq 17 at device 28.5 on pci0
                                        pci7: <acpi pci="" bus="">on pcib6
                                        em5: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff,0xfebdc000-0xfebdffff irq 17 at device 0.0 on pci7
                                        em5: Using MSIX interrupts with 3 vectors
                                        em5: Ethernet address: 00:90:7f:9f:5f:70
                                        em5: netmap queues/slots: TX 1/1024, RX 1/1024
                                        uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a="">port 0x7080-0x709f irq 23 at device 29.0 on pci0
                                        usbus0 on uhci0
                                        uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b="">port 0x7000-0x701f irq 19 at device 29.1 on pci0
                                        usbus1 on uhci1
                                        uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c="">port 0x6c00-0x6c1f irq 18 at device 29.2 on pci0
                                        usbus2 on uhci2
                                        uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d="">port 0x6880-0x689f irq 16 at device 29.3 on pci0
                                        usbus3 on uhci3
                                        ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xfe4ff800-0xfe4ffbff irq 23 at device 29.7 on pci0
                                        usbus4: EHCI version 1.0
                                        usbus4 on ehci0
                                        pcib7: <acpi pci-pci="" bridge="">at device 30.0 on pci0
                                        pci1: <acpi pci="" bus="">on pcib7
                                        fxp0: <intel 10="" 100="" 82801gb="" (ich7)="" ethernet="">port 0x8c00-0x8c3f mem 0xfe5ff000-0xfe5fffff irq 20 at device 8.0 on pci1
                                        miibus0: <mii bus="">on fxp0
                                        inphy0: <i82562et 10="" 100="" media="" interface="">PHY 1 on miibus0
                                        inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
                                        fxp0: Ethernet address: 00:90:7f:9f:5f:6a
                                        isab0: <pci-isa bridge="">at device 31.0 on pci0
                                        isa0: <isa bus="">on isab0
                                        atapci0: <intel ich7="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
                                        ata0: <ata channel="">at channel 0 on atapci0
                                        atapci1: <intel ich7="" sata300="" controller="">port 0x7c00-0x7c07,0x7880-0x7883,0x7800-0x7807,0x7480-0x7483,0x7400-0x740f mem 0xfe4ffc00-0xfe4fffff irq 19 at device 31.2 on pci0
                                        ata2: <ata channel="">at channel 0 on atapci1
                                        ata3: <ata channel="">at channel 1 on atapci1
                                        acpi_button0: <power button="">on acpi0
                                        uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
                                        uart0: console (115200,n,8,1)
                                        uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
                                        ppc0: <parallel port="">port 0x378-0x37f irq 7 on acpi0
                                        ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
                                        ppbus0: <parallel port="" bus="">on ppc0
                                        lpt0: <printer>on ppbus0
                                        lpt0: Interrupt-driven port
                                        ppi0: <parallel i="" o="">on ppbus0
                                        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]
                                        est0: <enhanced speedstep="" frequency="" control="">on cpu0
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est0 attach returned 6
                                        est1: <enhanced speedstep="" frequency="" control="">on cpu1
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est1 attach returned 6
                                        est2: <enhanced speedstep="" frequency="" control="">on cpu2
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est2 attach returned 6
                                        est3: <enhanced speedstep="" frequency="" control="">on cpu3
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est3 attach returned 6
                                        Timecounters tick every 1.000 msec
                                        random: unblocking device.
                                        usbus0: 12Mbps Full Speed USB v1.0
                                        usbus1: 12Mbps Full Speed USB v1.0
                                        usbus2: 12Mbps Full Speed USB v1.0
                                        usbus3: 12Mbps Full Speed USB v1.0
                                        ugen0.1: <intel>at usbus0
                                        uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
                                        ugen1.1: <intel>at usbus1
                                        uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
                                        ugen2.1: <intel>at usbus2
                                        uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
                                        ugen3.1: <intel>at usbus3
                                        uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
                                        usbus4: 480Mbps High Speed USB v2.0
                                        ugen4.1: <intel>at usbus4
                                        uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
                                        uhub0: 2 ports with 2 removable, self powered
                                        uhub1: 2 ports with 2 removable, self powered
                                        uhub2: 2 ports with 2 removable, self powered
                                        uhub3: 2 ports with 2 removable, self powered
                                        uhub4: 8 ports with 8 removable, self powered
                                        ada0 at ata2 bus 0 scbus1 target 0 lun 0
                                        ada0: <samsung hm250ji="" hs100-10="">ATA8-ACS SATA 1.x device
                                        ada0: Serial Number S15YJD0PB08244
                                        ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes)
                                        ada0: 238475MB (488397168 512 byte sectors)
                                        ada0: Previously was known as ad4
                                        SMP: AP CPU #2 Launched!
                                        SMP: AP CPU #1 Launched!
                                        SMP: AP CPU #3 Launched!
                                        Timecounter "TSC-low" frequency 1163774381 Hz quality 1000
                                        Trying to mount root from ufs:/dev/ufsid/5996b7217d4aca1d [rw]...
                                        coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
                                        est0: <enhanced speedstep="" frequency="" control="">on cpu0
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est0 attach returned 6
                                        coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1
                                        est1: <enhanced speedstep="" frequency="" control="">on cpu1
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est1 attach returned 6
                                        coretemp2: <cpu on-die="" thermal="" sensors="">on cpu2
                                        est2: <enhanced speedstep="" frequency="" control="">on cpu2
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est2 attach returned 6
                                        coretemp3: <cpu on-die="" thermal="" sensors="">on cpu3
                                        est3: <enhanced speedstep="" frequency="" control="">on cpu3
                                        est: CPU supports Enhanced Speedstep, but is not recognized.
                                        est: cpu_vendor GenuineIntel, msr 616072506000725
                                        device_attach: est3 attach returned 6
                                        em0: link state changed to UP
                                        pflog0: promiscuous mode enabled
                                        em1: link state changed to UP
                                        fxp0: link state changed to DOWN
                                        em0: Watchdog timeout Queue[0]-- resetting
                                        Interface is RUNNING and ACTIVE
                                        em0: TX Queue 0 ------
                                        em0: hw tdh = 990, hw tdt = 950
                                        em0: Tx Queue Status = -2147483648
                                        em0: TX descriptors avail = 40
                                        em0: Tx Descriptors avail failure = 31
                                        em0: RX Queue 0 ------
                                        em0: hw rdh = 767, hw rdt = 766
                                        em0: RX discarded packets = 0
                                        em0: RX Next to Check = 767
                                        em0: RX Next to Refresh = 766
                                        em0: link state changed to DOWN
                                        em0: link state changed to UP
                                        em1: Watchdog timeout Queue[0]-- resetting
                                        Interface is RUNNING and ACTIVE
                                        em1: TX Queue 0 ------
                                        em1: hw tdh = 909, hw tdt = 869
                                        em1: Tx Queue Status = -2147483648
                                        em1: TX descriptors avail = 40
                                        em1: Tx Descriptors avail failure = 2
                                        em1: RX Queue 0 ------
                                        em1: hw rdh = 800, hw rdt = 799
                                        em1: RX discarded packets = 0
                                        em1: RX Next to Check = 800
                                        em1: RX Next to Refresh = 799
                                        em1: link state changed to DOWN
                                        em1: link state changed to UP
                                        [2.3.4-RELEASE][root@pfSense.JTT.local]/root:</enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></samsung></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></enhanced></enhanced></enhanced></enhanced></at></keyboard></generic></system></parallel></printer></parallel></parallel></power></ata></ata></intel></ata></intel></isa></pci-isa></i82562et></mii></intel></acpi></acpi></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel></vga-compatible></acpi></acpi></at></at></acpi></acpi></acpi></acpi></software></version></software,></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave,osxsave></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></enhanced></cpu></enhanced></cpu></enhanced></cpu></enhanced></cpu></samsung></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></enhanced></enhanced></enhanced></enhanced></at></keyboard></generic></system></parallel></printer></parallel></parallel></power></ata></ata></intel></ata></intel></isa></pci-isa></i82562et></mii></intel></acpi></acpi></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel></vga-compatible></acpi></acpi></at></at></acpi></acpi></acpi></acpi></software></version></software,></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave,osxsave></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
                                        • B
                                          Billyboy
                                          last edited by

                                          @stephenw10:

                                          Hmm, and you're actually pulling the cable from the port on the xtm5?

                                          What does ifconfig show for that port during that time?

                                          Steve

                                          Yes, I am pulling the cable directly at the box.

                                          That's the ifconfig output after pulling the cable:

                                          em4: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
                                            options=42098 <vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso>ether 00:90:7f:84:61:dc
                                            hwaddr 00:90:7f:84:61:dc
                                            inet6 fe80::290:7fff:fe84:61dc%em4 prefixlen 64 scopeid 0x5
                                            inet 192.168.245.101 netmask 0xffffff00 broadcast 192.168.245.255
                                            inet 192.168.245.100 netmask 0xffffff00 broadcast 192.168.245.255 vhid 5
                                            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (1000baseT <full-duplex>)
                                            status: active
                                            carp: MASTER vhid 5 advbase 1 advskew 0</full-duplex></performnud,auto_linklocal></vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,vlan_hwtso></up,broadcast,running,promisc,simplex,multicast>

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

                                            @blaxx

                                            This looks bad:

                                            em0: Watchdog timeout Queue[0]-- resetting
                                            

                                            Something is giving those interfaces a hard time.

                                            @Billyboy

                                            Hmm, I've never seen that before on any interface. It's hard to imagine what could allow the driver to report that as UP.

                                            Steve

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