[SDBUG] Watchdog Timeout in 5.1 and above, Help!

[Raymundo M. Vega]

I have seen this message (sis driver) when the config option
in /etc/rc.conf is not set to a fixed media and mediaopt.

Fix it and try, it may solve the problem.

raymundo

Dave Smith wrote:

>I would be tempted to disable the watchdog timeout.  We
>see great spikes in the amount of CPU usage for short
>periods of time on our mail servers.  That may be incorrectly
>triggering the watchdog timeout.
>
>I don't run 5.1 on our mail servers.  I have stuck with
>4.8/4.9 until they declare that 5.1 is ready for production
>use.
>
>Dave Smith
>
>
>On Mon, Mar 29, 2004 at 01:58:50PM -0800, Joseph A. Kitzman wrote:
>  
>
>>Hey all,
>>
>>Lately I've been having issues with a few of my FreeBSD servers. I'm in the
>>middle of trying to fix the problem, but it's taking me a long time and I'm
>>hoping one of you may know of a solution. Basically, all my production
>>servers are running 5.1 or above and they're all using identical hardware.
>>When a server starts pushing a decent amount of traffic (burst traffic or
>>file transfers), it will suddenly drop offline, the driver throws a Watchdog
>>timeout and attempts to re-negotiate with the switch. It will never come
>>back online, and the process will repeat every couple minutes until I
>>reboot. It only seems to happen every 24-48 hours.
>>
>>Mar 28 23:50:27 unixtest kernel: em0: watchdog timeout -- resetting
>>Mar 28 23:50:29 unixtest kernel: em0: Link is up 100 Mbps Full Duplex
>>Mar 28 23:50:38 unixtest kernel: em0: watchdog timeout -- resetting
>>Mar 28 23:50:40 unixtest kernel: em0: Link is up 100 Mbps Full Duplex
>>Mar 28 23:50:46 unixtest kernel: em0: watchdog timeout -- resetting
>>Mar 28 23:50:48 unixtest kernel: em0: Link is up 100 Mbps Full Duplex
>>Mar 28 23:52:41 unixtest kernel: em0: watchdog timeout -- resetting
>>Mar 28 23:52:43 unixtest kernel: em0: Link is up 100 Mbps Full Duplex
>>...and so on...
>>
>>The servers were originally using RealTek 8139 10/100BaseTX onboard NICs. I
>>figured the failure may have been the fault of cheap hardware, so I replaced
>>them with Intel PRO/1000 Server PCI NICs. Even with the new hardware, the
>>machines are still having watchdog timeouts and dropping offline. Some are
>>located in house, some are at other datacenters.. all experience the same
>>issues. The problems did not occur in FreeBSD 5.0. Here's what I've tried so
>>far:
>>
>>1. Replace RealTeks with Intel PROs -- Didn't work.
>>2. Disable ACPI -- Didn't work.
>>3. BIOS update for the mobos -- Didn't work.
>>4. Plug test server into an HP Procurve instead of a Cisco Catalyst -- 
>>Didn't work.
>>
>>Going to try:
>>
>>1. Hard locking the media type and media options in driver config.
>>2. ???
>>3. Microsoft Windows.
>>
>>Google turned up issues people were having with the EM driver in FreeBSD
>>4.8, however that fix is for a much older version of the driver. As far as I
>>can tell, it's no longer applicable.
>>
>>Help!
>>
>>-Joe
>>
>>--------------------------
>>
>>[root at unixtest]:/usr/src/sys/dev/em# dmesg
>>Copyright (c) 1992-2004 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 5.2.1-RELEASE-p3 #2: Thu Mar 25 08:57:26 PST 2004
>>    root@:/usr/obj/usr/src/sys/UNIXTEST
>>Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a42000.
>>Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a421f4.
>>ACPI APIC Table: <VIA601 AWRDACPI>
>>Timecounter "i8254" frequency 1193182 Hz quality 0
>>CPU: Intel(R) Pentium(R) III CPU             1200MHz (1196.95-MHz 686-class
>>CPU)
>>  Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
>>
>>Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
>>CMOV,PAT,PSE36,MMX,FXSR,SSE>
>>real memory  = 259981312 (247 MB)
>>avail memory = 242892800 (231 MB)
>>ioapic0 <Version 1.1> irqs 0-23 on motherboard
>>Pentium Pro MTRR support enabled
>>npx0: [FAST]
>>npx0: <math processor> on motherboard
>>npx0: INT 16 interface
>>acpi0: <VIA601 MSI ACPI> on motherboard
>>pcibios: BIOS version 2.10
>>Using $PIR table, 6 entries at 0xc00fddf0
>>acpi0: Power Button (fixed)
>>Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
>>acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
>>acpi_cpu0: <CPU> on acpi0
>>acpi_button0: <Power Button> on acpi0
>>acpi_button1: <Sleep Button> on acpi0
>>pcib0: <ACPI Host-PCI bridge> port
>>0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0
>>pci0: <ACPI PCI bus> on pcib0
>>pcib0: slot 7 INTD is routed to irq 11
>>pcib0: slot 7 INTD is routed to irq 11
>>agp0: <VIA Generic host to PCI bridge> mem 0xd0000000-0xd1ffffff at device
>>0.0 on pci0
>>pcib1: <PCI-PCI bridge> at device 1.0 on pci0
>>pci1: <PCI bus> on pcib1
>>pcib1: slot 0 INTA is routed to irq 16
>>pci1: <display, VGA> at device 0.0 (no driver attached)
>>isab0: <PCI-ISA bridge> at device 7.0 on pci0
>>isa0: <ISA bus> on isab0
>>atapci0: <VIA 82C686B UDMA100 controller> port 0xd000-0xd00f at device 7.1
>>on pci0
>>ata0: at 0x1f0 irq 14 on atapci0
>>ata0: [MPSAFE]
>>ata1: at 0x170 irq 15 on atapci0
>>ata1: [MPSAFE]
>>uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 11 at device 7.2
>>on pci0
>>usb0: <VIA 83C572 USB controller> on uhci0
>>usb0: USB revision 1.0
>>uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>>uhub0: 2 ports with 2 removable, self powered
>>uhci1: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 11 at device 7.3
>>on pci0
>>usb1: <VIA 83C572 USB controller> on uhci1
>>usb1: USB revision 1.0
>>uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>>uhub1: 2 ports with 2 removable, self powered
>>pci0: <old> at device 7.4 (no driver attached)
>>em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port
>>0xdc00-0xdc3f mem 0xd6000000-0xd601ffff,0xd6020000-0xd603ffff irq 17 at
>>device 9.0 on pci0
>>em0:  Speed:N/A  Duplex:N/A
>>rl0: <RealTek 8139 10/100BaseTX> port 0xe000-0xe0ff mem
>>0xd6040000-0xd60400ff irq 19 at device 14.0 on pci0
>>rl0: Ethernet address: 00:0c:76:28:48:bf
>>miibus0: <MII bus> on rl0
>>rlphy0: <RealTek internal media interface> on miibus0
>>rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>>fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port
>>0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
>>fdc0: FIFO enabled, 8 bytes threshold
>>fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>>sio0 port 0x3f8-0x3ff irq 4 on acpi0
>>sio0: type 16550A
>>ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
>>ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
>>ppc0: FIFO with 16/16/8 bytes threshold
>>ppbus0: <Parallel port bus> on ppc0
>>plip0: <PLIP network interface> on ppbus0
>>lpt0: <Printer> on ppbus0
>>lpt0: Interrupt-driven port
>>ppi0: <Parallel I/O> on ppbus0
>>atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
>>atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
>>kbd0 at atkbd0
>>psm0: <PS/2 Mouse> irq 12 on atkbdc0
>>psm0: model IntelliMouse, device ID 3
>>orm0: <Option ROM> at iomem 0xc0000-0xcbfff on isa0
>>pmtimer0 on isa0
>>sc0: <System console> at flags 0x100 on isa0
>>sc0: VGA <16 virtual consoles, flags=0x300>
>>sio1: configured irq 3 not in bitmap of probed irqs 0
>>sio1: port may not be enabled
>>vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
>>Timecounter "TSC" frequency 1196954171 Hz quality 800
>>Timecounters tick every 10.000 msec
>>ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to
>>accept, logging limited to 10 packets/entry by default
>>GEOM: create disk ad0 dp=0xc2d03060
>>ad0: 39205MB <Maxtor 6E040L0> [79656/16/63] at ata0-master UDMA100
>>GEOM: create disk ad1 dp=0xc2cbdb60
>>ad1: 114473MB <WDC WD1200BB-22CAA1> [232581/16/63] at ata0-slave UDMA100
>>Mounting root from ufs:/dev/ad0s1a
>>em0: Link is up 100 Mbps Full Duplex
>>
>>_______________________________________________
>>San Diego's BSD Users Group
>>http://www.sdbug.org
>>SDBUG at sdbug.org
>>http://www.sdbug.org/mailman/listinfo/sdbug
>>
>>    
>>
>
>  
>