[pfSense Support] em0: Watchdog timeout -- resetting

2009-01-03 Thread Nathan Eisenberg 








Hello,

 

I am deploying a new set of firewall boxes using PFSense
1.2.1.  These boxes have 4GB of RAM, Intel Quad Core CPUs, and a PCI-E
Intel 4 Port 10/100/1000 NIC (em0-3) in addition to the 2 onboard 10/100/1000
NICs (em4-5).

 

The Intel NIC seems to go to pieces whenever load is passed
through it; the two onboard NICs do fine.   Since I'm using a Cisco
switch, the port takes about 30 seconds to start forwarding packets after the
issue passes.  I've seen this on my home PFSense box, as well (completely
different hardware config), but since I'm not using a Cisco switch at home, I
don't notice its effects as severely.

 

The error I am seeing is "em0: Watchdog Timeout --
Resetting", which seems to have several root causes.  I have tried
disabling ACPI, both in the BIOS, and in the bootloader.  I have disabled
all nonessential devices in the BIOS (except USB), and swapped all cables out
(they're all brand new CAT6).  The problem occurs if em0 is connected to a
switch, or to my laptop via crossover.  After three hours of Googling, I
am stumped.

 

Help?

 

dmesg follows (although em0 and em1 have been replaced with
em4 and em5 temporarily).

 

$ dmesg

Copyright (c) 1992-2008 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 7.0-RELEASE-p7 #0: Thu Dec 25 14:39:15 EST 2008

    sullr...@freebsd7-releng_1_2_1.pfsense.org:/usr/obj.pfSense/usr/src/sys/pfSense_SMP.7

Timecounter "i8254" frequency 1193182 Hz quality 0

CPU: Intel(R) Xeon(R)
CPU   E5410  @
2.33GHz (2333.43-MHz 686-class CPU)

  Origin = "GenuineIntel"  Id =
0x1067a  Stepping = 10

 
Features=0xbfebfbff

  Features2=0x40ce3bd,>

  AMD Features=0x2010

  AMD Features2=0x1

  Cores per package: 4

real memory  = 2146467840 (2047 MB)

avail memory = 2090897408 (1994 MB)

MPTable: 

FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs

 cpu0 (BSP): APIC ID:  0

 cpu1 (AP): APIC ID:  1

 cpu2 (AP): APIC ID:  2

 cpu3 (AP): APIC ID:  3

ioapic0: Assuming intbase of 0

ioapic1: Assuming intbase of 24

ioapic0  irqs 0-23 on motherboard

ioapic1  irqs 24-47 on motherboard

wlan: mac acl policy registered

kbd1 at kbdmux0

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112,
RF2413, RF5413)

hptrr: HPT RocketRAID controller driver v1.1 (Dec 25 2008 14:38:55)

cryptosoft0:  on motherboard

cpu0 on motherboard

est0:  on cpu0

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est0 attach returned 6

p4tcc0:  on cpu0

cpu1 on motherboard

est1:  on cpu1

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est1 attach returned 6

p4tcc1:  on cpu1

cpu2 on motherboard

est2:  on cpu2

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est2 attach returned 6

p4tcc2:  on cpu2

cpu3 on motherboard

est3:  on cpu3

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est3 attach returned 6

p4tcc3:  on cpu3

pcib0:  pcibus 0 on
motherboard

pci0:  on pcib0

pcib1:  irq 24 at device 1.0 on pci0

pci1:  on pcib1

pcib2:  at device 0.0 on pci1

pci2:  on pcib2

pcib3:  at device 2.0 on pci2

pci3:  on pcib3

pcib3: unable to route slot 0 INTB

em0:  port 0x2000-0x201f mem 0xd802-0xd803,0xd800-0xd801
irq 11 at device 0.0 on pci3

em0: Using MSI interrupt

em0: Ethernet address: 00:15:17:90:09:c1

em0: [FILTER]

em1:  port 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805
irq 28 at device 0.1 on pci3

em1: Using MSI interrupt

em1: Ethernet address: 00:15:17:90:09:c0

em1: [FILTER]

pcib4:  at device 4.0 on pci2

pci4:  on pcib4

pcib4: unable to route slot 0 INTB

em2:  port 0x3000-0x301f mem 0xd812-0xd813,0xd810-0xd811
irq 11 at device 0.0 on pci4

em2: Using MSI interrupt

em2: Ethernet address: 00:15:17:90:09:c3

em2: [FILTER]

em3:  port 0x3020-0x303f mem 0xd816-0xd817,0xd814-0xd815
irq 28 at device 0.1 on pci4

em3: Using MSI interrupt

em3: Ethernet address: 00:15:17:90:09:c2

em3: [FILTER]

pcib5:  irq 28 at device 5.0 on pci0

pci5:  on pcib5

pcib6:  irq 28 at device 0.0
on pci5

pci6:  on pcib6

pcib6: unable to route slot 0 INTA

pcib7:  irq 11 at device 0.0 on pci6

pci7:  on pcib7

pcib8:  irq 44 at device 2.0
on pci6

pci8:  on pcib8

em4:  port 0x4000-0x401f mem 0xd822-0xd823,0xd820-0xd821
irq 44 at device 0.0 on pci8

em4: Using MSI interrupt

em4: Ethernet address: 00:30:48:c4:98:4c

em4: [FILTER]

em5:  port 0x4020-0x403f mem 0xd826-0xd827,0xd824-0xd825
irq 40 at device 0.1 on pci8

em5: Using MSI interrupt

em5: Ethernet address: 00:

[pfSense Support] rebooting and pftpx error messages

2009-01-03 Thread Alexandre F. Guimaraes 


I´ve embedded version using 1.2.1 built on Thu Dec 25 14:48:40 EST 2008 
with

4GB CF Card.

The server reboot by it self two or three times per day, since I have
installed this version I got the pftpx[1262]: #1 server timeout error
message in my log.


How the way to correct or stop these messages?


Jan 3 23:30:15 pftpx[1262]: #9 server timeout
Jan 3 23:30:15 pftpx[1262]: #9 server timeout
Jan 3 23:24:58 pftpx[1262]: #8 client reset connection
Jan 3 23:24:58 pftpx[1262]: #8 client reset connection
Jan 3 23:18:10 pftpx[1262]: #6 server timeout
Jan 3 23:18:10 pftpx[1262]: #6 server timeout
Jan 3 23:11:47 pftpx[1262]: #5 client reset connection
Jan 3 23:11:47 pftpx[1262]: #5 client reset connection
Jan 3 23:07:17 pftpx[1262]: #4 server timeout
Jan 3 23:07:17 pftpx[1262]: #4 server timeout
Jan 3 23:04:50 pftpx[1262]: #3 server timeout
Jan 3 23:04:50 pftpx[1262]: #3 server timeout
Jan 3 22:50:25 pftpx[1262]: #2 server timeout
Jan 3 22:50:25 pftpx[1262]: #2 server timeout
Jan 3 22:33:07 pftpx[1262]: #1 server timeout
Jan 3 22:33:07 pftpx[1262]: #1 server timeout


Alexandre



-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org

Re: [pfSense Support] em0: Watchdog timeout -- resetting

2009-01-03 Thread apiase...@midatlanticbb.com 
Can't help with your pfsense problem, but it might help to configure 
this on your switch.


"spanning-tree portfast" Configured on your cisco switch will change the 
port to a forwarding state immediately.


Nathan Eisenberg wrote:


Hello,

 

I am deploying a new set of firewall boxes using PFSense 1.2.1.  These 
boxes have 4GB of RAM, Intel Quad Core CPUs, and a PCI-E Intel 4 Port 
10/100/1000 NIC (em0-3) in addition to the 2 onboard 10/100/1000 NICs 
(em4-5).


 

The Intel NIC seems to go to pieces whenever load is passed through 
it; the two onboard NICs do fine.   Since I'm using a Cisco switch, 
the port takes about 30 seconds to start forwarding packets after the 
issue passes.  I've seen this on my home PFSense box, as well 
(completely different hardware config), but since I'm not using a 
Cisco switch at home, I don't notice its effects as severely.


 

The error I am seeing is "em0: Watchdog Timeout -- Resetting", which 
seems to have several root causes.  I have tried disabling ACPI, both 
in the BIOS, and in the bootloader.  I have disabled all nonessential 
devices in the BIOS (except USB), and swapped all cables out (they're 
all brand new CAT6).  The problem occurs if em0 is connected to a 
switch, or to my laptop via crossover.  After three hours of Googling, 
I am stumped.


 


Help?

 

dmesg follows (although em0 and em1 have been replaced with em4 and 
em5 temporarily).


 


$ dmesg

Copyright (c) 1992-2008 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 7.0-RELEASE-p7 #0: Thu Dec 25 14:39:15 EST 2008


sullr...@freebsd7-releng_1_2_1.pfsense.org:/usr/obj.pfSense/usr/src/sys/pfSense_SMP.7 



Timecounter "i8254" frequency 1193182 Hz quality 0

CPU: Intel(R) Xeon(R) CPU   E5410  @ 2.33GHz (2333.43-MHz 
686-class CPU)


  Origin = "GenuineIntel"  Id = 0x1067a  Stepping = 10

  
Features=0xbfebfbff


  
Features2=0x40ce3bd,>


  AMD Features=0x2010

  AMD Features2=0x1

  Cores per package: 4

real memory  = 2146467840 (2047 MB)

avail memory = 2090897408 (1994 MB)

MPTable: 

FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs

 cpu0 (BSP): APIC ID:  0

 cpu1 (AP): APIC ID:  1

 cpu2 (AP): APIC ID:  2

 cpu3 (AP): APIC ID:  3

ioapic0: Assuming intbase of 0

ioapic1: Assuming intbase of 24

ioapic0  irqs 0-23 on motherboard

ioapic1  irqs 24-47 on motherboard

wlan: mac acl policy registered

kbd1 at kbdmux0

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)

hptrr: HPT RocketRAID controller driver v1.1 (Dec 25 2008 14:38:55)

cryptosoft0:  on motherboard

cpu0 on motherboard

est0:  on cpu0

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est0 attach returned 6

p4tcc0:  on cpu0

cpu1 on motherboard

est1:  on cpu1

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est1 attach returned 6

p4tcc1:  on cpu1

cpu2 on motherboard

est2:  on cpu2

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est2 attach returned 6

p4tcc2:  on cpu2

cpu3 on motherboard

est3:  on cpu3

est: CPU supports Enhanced Speedstep, but is not recognized.

est: cpu_vendor GenuineIntel, msr 721072106000721

device_attach: est3 attach returned 6

p4tcc3:  on cpu3

pcib0:  pcibus 0 on motherboard

pci0:  on pcib0

pcib1:  irq 24 at device 1.0 on pci0

pci1:  on pcib1

pcib2:  at device 0.0 on pci1

pci2:  on pcib2

pcib3:  at device 2.0 on pci2

pci3:  on pcib3

pcib3: unable to route slot 0 INTB

em0:  port 
0x2000-0x201f mem 0xd802-0xd803,0xd800-0xd801 irq 11 
at device 0.0 on pci3


em0: Using MSI interrupt

em0: Ethernet address: 00:15:17:90:09:c1

em0: [FILTER]

em1:  port 
0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 28 
at device 0.1 on pci3


em1: Using MSI interrupt

em1: Ethernet address: 00:15:17:90:09:c0

em1: [FILTER]

pcib4:  at device 4.0 on pci2

pci4:  on pcib4

pcib4: unable to route slot 0 INTB

em2:  port 
0x3000-0x301f mem 0xd812-0xd813,0xd810-0xd811 irq 11 
at device 0.0 on pci4


em2: Using MSI interrupt

em2: Ethernet address: 00:15:17:90:09:c3

em2: [FILTER]

em3:  port 
0x3020-0x303f mem 0xd816-0xd817,0xd814-0xd815 irq 28 
at device 0.1 on pci4


em3: Using MSI interrupt

em3: Ethernet address: 00:15:17:90:09:c2

em3: [FILTER]

pcib5:  irq 28 at device 5.0 on pci0

pci5:  on pcib5

pcib6:  irq 28 at device 0.0 on pci5

pci6:  on pcib6

pcib6: unable to route slot 0 INTA

pcib7:  irq 11 at device 0.0 on pci6

pci7:  on pcib7

pcib8:  irq 44 at device 2.0 o