pfSense Gold Subscription

Author Topic: Watchdog timeouts after upgrade of embedded [solved]  (Read 3247 times)

0 Members and 1 Guest are viewing this topic.

Offline ridnhard19

  • Jr. Member
  • **
  • Posts: 49
  • Karma: +0/-0
    • View Profile
Watchdog timeouts after upgrade of embedded [solved]
« on: February 26, 2008, 09:15:49 pm »
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:

Quote
re1: watchdog timeout

I'm using a firebox x700.

here's my dmesg output:
Quote
Copyright (c) 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 Interrupt Routing Table: 11 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 8139C+ 10/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 8139C+ 10/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 8139C+ 10/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 8139C+ 10/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 8139C+ 10/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 8139C+ 10/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 channel 0> on atapci0
ata1: <ATA channel 1> 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

« Last Edit: February 27, 2008, 06:09:14 pm by ridnhard19 »

Offline ridnhard19

  • Jr. Member
  • **
  • Posts: 49
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #1 on: February 26, 2008, 10:17:15 pm »
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!
« Last Edit: February 26, 2008, 10:30:16 pm by ridnhard19 »

Offline mOjO

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #2 on: February 27, 2008, 09:24:10 am »
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.

Offline hoba

  • Administrator
  • Hero Member
  • *****
  • Posts: 5837
  • Karma: +3/-0
  • What was the problem to this solution again?
    • View Profile
    • pfSense
Re: Watchdog timeouts after upgrade of embedded
« Reply #3 on: February 27, 2008, 09:26:08 am »
See http://devwiki.pfsense.org/BootOptions for bootoptions and how to make acpi disabled on bootup by default.

Offline mOjO

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #4 on: February 27, 2008, 09:28:05 am »
try disabling ACPI via this:
http://devwiki.pfsense.org/BootOptions

Offline ridnhard19

  • Jr. Member
  • **
  • Posts: 49
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #5 on: February 27, 2008, 11:44:24 am »
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.

Offline ridnhard19

  • Jr. Member
  • **
  • Posts: 49
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #6 on: February 27, 2008, 06:06:41 pm »
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.

Offline RonpfS

  • Full Member
  • ***
  • Posts: 129
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded
« Reply #7 on: February 27, 2008, 06:52:13 pm »
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


« Last Edit: March 06, 2008, 01:25:56 pm by RonpfS »

Offline ridnhard19

  • Jr. Member
  • **
  • Posts: 49
  • Karma: +0/-0
    • View Profile
Re: Watchdog timeouts after upgrade of embedded [solved]
« Reply #8 on: February 27, 2008, 07:09:38 pm »
I would not think so; I sure don't have a need.  Maybe this setting should be default then?