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

    Watchdog timeouts after upgrade of embedded [solved]

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    9 Posts 4 Posters 7.6k 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.
    • R Offline
      ridnhard19
      last edited by

      dropped connections and slow web gui for admin interface.  Was running 1.2-RC4 w/ no issues before.  I did the embedded upgrade and now am getting watchdog errors:

      re1: watchdog timeout

      I'm using a firebox x700.

      here's my dmesg output:

      Copyright © 1992-2007 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 6.2-RELEASE-p11 #0: Sun Feb 24 16:38:29 EST 2008
          sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense_wrap.6
      Timecounter "i8254" frequency 1193182 Hz quality 0
      CPU: Intel(R) Celeron(TM) CPU                1200MHz (1202.73-MHz 686-class CPU)
        Origin = "GenuineIntel"  Id = 0x6b4  Stepping = 4
        Features=0x383f9ff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse>real memory  = 268435456 (256 MB)
      avail memory = 253267968 (241 MB)
      wlan: mac acl policy registered
      ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
      cpu0 on motherboard
      pcib0: <intel 82815="" (i815="" gmch)="" host="" to="" hub="" bridge="">pcibus 0 on motherboard
      pir0: <pci 11="" interrupt="" routing="" table:="" entries="">on motherboard
      $PIR: Using invalid BIOS IRQ 9 from 2.13.INTA for link 0x63
      pci0: <pci bus="">on pcib0
      pcib1: <pcibios pci-pci="" bridge="">at device 30.0 on pci0
      pci2: <pci bus="">on pcib1
      pci2: <unknown>at device 6.0 (no driver attached)
      re0: <realtek 10="" 8139c+="" 100basetx="">port 0xd500-0xd5ff mem 0xefefa000-0xefefa1ff irq 10 at device 9.0 on pci2
      miibus0: <mii bus="">on re0
      rlphy0: <realtek internal="" media="" interface="">on miibus0
      rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re0: Ethernet address: 00:90:7f:30:f2:81
      re0: [FAST]
      re1: <realtek 10="" 8139c+="" 100basetx="">port 0xd600-0xd6ff mem 0xefefb000-0xefefb1ff irq 5 at device 10.0 on pci2
      miibus1: <mii bus="">on re1
      rlphy1: <realtek internal="" media="" interface="">on miibus1
      rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re1: Ethernet address: 00:90:7f:30:f2:82
      re1: [FAST]
      re2: <realtek 10="" 8139c+="" 100basetx="">port 0xd900-0xd9ff mem 0xefefc000-0xefefc1ff irq 11 at device 11.0 on pci2
      miibus2: <mii bus="">on re2
      rlphy2: <realtek internal="" media="" interface="">on miibus2
      rlphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re2: Ethernet address: 00:90:7f:30:f2:83
      re2: [FAST]
      re3: <realtek 10="" 8139c+="" 100basetx="">port 0xda00-0xdaff mem 0xefefd000-0xefefd1ff irq 12 at device 12.0 on pci2
      miibus3: <mii bus="">on re3
      rlphy3: <realtek internal="" media="" interface="">on miibus3
      rlphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re3: Ethernet address: 00:90:7f:30:f2:84
      re3: [FAST]
      re4: <realtek 10="" 8139c+="" 100basetx="">port 0xdd00-0xddff mem 0xefefe000-0xefefe1ff irq 9 at device 13.0 on pci2
      miibus4: <mii bus="">on re4
      rlphy4: <realtek internal="" media="" interface="">on miibus4
      rlphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re4: Ethernet address: 00:90:7f:30:f2:85
      re4: [FAST]
      re5: <realtek 10="" 8139c+="" 100basetx="">port 0xde00-0xdeff mem 0xefeff000-0xefeff1ff irq 6 at device 14.0 on pci2
      miibus5: <mii bus="">on re5
      rlphy5: <realtek internal="" media="" interface="">on miibus5
      rlphy5:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      re5: Ethernet address: 00:90:7f:30:f2:86
      re5: [FAST]
      isab0: <pci-isa bridge="">at device 31.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <intel ich2="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.1 on pci0
      ata0: <ata 0="" channel="">on atapci0
      ata1: <ata 1="" channel="">on atapci0
      orm0: <isa option="" rom="">at iomem 0xe0000-0xe0fff on isa0
      ppc0: <parallel port="">at port 0x378-0x37f irq 7 on isa0
      ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
      ppc0: FIFO with 16/16/16 bytes threshold
      ppbus0: <parallel port="" bus="">on ppc0
      ppi0: <parallel i="" o="">on ppbus0
      sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
      sio0: type 16550A, console
      sio1: configured irq 3 not in bitmap of probed irqs 0
      sio1: port may not be enabled
      unknown: <pnp0c01>can't assign resources (memory)
      speaker0: <pc speaker="">at port 0x61 on isa0
      unknown: <pnp0501>can't assign resources (port)
      unknown: <pnp0401>can't assign resources (port)
      RTC BIOS diagnostic error 20 <config_unit>Timecounter "TSC" frequency 1202733650 Hz quality 800
      Timecounters tick every 10.000 msec
      Fast IPsec: Initialized Security Association Processing.
      ad0: 1911MB <transcend 20070831="">at ata0-master PIO4
      GEOM_LABEL: Label for provider ad0a is ufs/pfSense.
      GEOM_LABEL: Label for provider ad0d is ufs/pfSenseCfg.
      Trying to mount root from ufs:/dev/ufs/pfSense
      re0: link state changed to UP
      re1: link state changed to UP
      re2: link state changed to DOWN
      re3: link state changed to DOWN
      re4: link state changed to DOWN
      re5: link state changed to UP
      re1: link state changed to DOWN
      re1: link state changed to UP
      re0: link state changed to DOWN
      re1: link state changed to DOWN
      re0: link state changed to UP
      re1: link state changed to UP
      re1: link state changed to DOWN
      re1: link state changed to UP
      re5: link state changed to DOWN
      pflog0: promiscuous mode enabled
      re5: link state changed to UP
      pflog0: promiscuous mode disabled
      pflog0: promiscuous mode enabled
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout
      re1: watchdog timeout</transcend></config_unit></pnp0401></pnp0501></pc></pnp0c01></parallel></parallel></parallel></isa></ata></ata></intel></isa></pci-isa></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></unknown></pci></pcibios></pci></pci></intel></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse>

      1 Reply Last reply Reply Quote 0
      • R Offline
        ridnhard19
        last edited by

        Update: I've re-flashed using the non-upgrade full version of 1.2-Embedded and started to manually configure the device. Didn't get very far and am seeing the watchdog errors again.  Please Help!

        1 Reply Last reply Reply Quote 0
        • M Offline
          mOjO
          last edited by

          not sure if it helps (never done an embedded install) but I was having the same issues on an OLD PC until I booted it up with ACPI disabled (option #2) on the pfSense boot menu.  The menu goes by very quickly and I have no idea if you can even access it via serial console on an embedded device but you should be able to modify the boot values from a shell.

          1 Reply Last reply Reply Quote 0
          • H Offline
            hoba
            last edited by

            See http://devwiki.pfsense.org/BootOptions for bootoptions and how to make acpi disabled on bootup by default.

            1 Reply Last reply Reply Quote 0
            • M Offline
              mOjO
              last edited by

              try disabling ACPI via this:
              http://devwiki.pfsense.org/BootOptions

              1 Reply Last reply Reply Quote 0
              • R Offline
                ridnhard19
                last edited by

                I'll give that a shot when I get home and let you all know what happens. My concern is that this was working fine with RC4.  I'm not sure what could of changed.

                1 Reply Last reply Reply Quote 0
                • R Offline
                  ridnhard19
                  last edited by

                  It WORKED! I'm thrilled, great suggestion and Thanks. But now i have to ask why I didn't have to do this before with the RC versions.

                  1 Reply Last reply Reply Quote 0
                  • RonpfSR Offline
                    RonpfS
                    last edited by

                    @ridnhard19:

                    It WORKED! I'm thrilled, great suggestion and Thanks. But now i have to ask why I didn't have to do this before with the RC versions.

                    Is there any need for ACPI in a pfsense application? ??  ???
                    Yes there is … it looks like when you disable ACPI in BSD, the interrupts are not mapped correctly.
                    I was getting all sorts of crashes with ACPI disabled and now that I enabled it things are running smoothly  ;D

                    2.4.5-RELEASE-p1 (amd64)
                    Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                    Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      ridnhard19
                      last edited by

                      I would not think so; I sure don't have a need.  Maybe this setting should be default then?

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