Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Jun 2008 16:40:12 -0700
From:      Rudy <crapsh@MonkeyBrains.NET>
To:        freebsd-net@freebsd.org
Subject:   Re: em0: watchdog timeout -- resetting
Message-ID:  <4853055C.2030303@MonkeyBrains.NET>
In-Reply-To: <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com>
References:  <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Jack Vogel wrote:
 > Did you ever install the fix to the 82573 NIC eeprom?

Just saw the "watchdog" error using an Intel Pro Quad PT card...
it has the '82571EB' chip on it.
  -- Do those cards need the eeprom 'fix'?
  -- or is related to kern/122928
  -- how does one go about disabling the watchdog?  (turning off acpi?)


Thanks,
Rudy


SYSTEM INFO:

# grep Exp /usr/src/sys/dev/em/if_em.c
/*$FreeBSD: src/sys/dev/em/if_em.c,v 1.184.2.3 2008/05/21 21:34:05 jfv Exp $*/

# pciconf -lv | grep -A 4 em2
em2@pci0:6:0:0: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 hdr=0x00
     vendor     = 'Intel Corporation'
     device     = '82571EB Gigabit Ethernet Controller'
     class      = network
     subclass   = ethernet

# sysctl dev.em.2
dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 6.9.5
dev.em.2.%driver: em
dev.em.2.%location: slot=0 function=0
dev.em.2.%pnpinfo: vendor=0x8086 device=0x10a4 subvendor=0x8086 subdevice=0x10a4 class=0x020000
dev.em.2.%parent: pci6
dev.em.2.debug: -1
dev.em.2.stats: -1
dev.em.2.rx_int_delay: 0
dev.em.2.tx_int_delay: 66
dev.em.2.rx_abs_int_delay: 66
dev.em.2.tx_abs_int_delay: 66
dev.em.2.rx_processing_limit: 100


# ifconfig em2
em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=1db<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,POLLING,VLAN_HWCSUM,TSO4>
         ether 00:15:17:78:99:72
         inet 10.10.30.154 netmask 0xfffffffc broadcast 10.10.30.155
         media: Ethernet autoselect (1000baseTX <full-duplex>)
         status: active

# uname -a
FreeBSD example.monkeybrains.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jun  3 16:43:19 PDT 2008 
root@buildbox.monkeybrains.net:/usr/obj/usr/src/sys/ROUTER  i386

# grep em2 /var/log/messages
Jun 11 23:08:34 example kernel: em2: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0x3000-0x301f 
mem 0xd8120000-0xd813ffff,0xd8100000-0xd811ffff irq 17 at device 0.0 on pci6
Jun 11 23:08:34 example kernel: em2: Using MSI interrupt
Jun 11 23:08:34 example kernel: em2: [FILTER]
Jun 11 23:08:34 example kernel: em2: Ethernet address: 00:15:17:78:99:72
Jun 11 23:18:08 example kernel: em2: link state changed to UP
Jun 13 00:27:22 example kernel: em2: watchdog timeout -- resetting
Jun 13 00:27:22 example kernel: em2: link state changed to DOWN
Jun 13 00:27:25 example kernel: em2: link state changed to UP
Jun 13 03:37:52 example kernel: em2: watchdog timeout -- resetting
Jun 13 03:37:52 example kernel: em2: link state changed to DOWN
Jun 13 03:37:55 example kernel: em2: link state changed to UP
Jun 13 05:17:18 example kernel: em2: watchdog timeout -- resetting
Jun 13 05:17:18 example kernel: em2: link state changed to DOWN
Jun 13 05:17:22 example kernel: em2: link state changed to UP
Jun 13 05:17:23 example kernel: em2: link state changed to DOWN
Jun 13 05:17:25 example kernel: em2: link state changed to UP
Jun 13 06:54:47 example kernel: em2: watchdog timeout -- resetting
Jun 13 06:54:47 example kernel: em2: link state changed to DOWN
Jun 13 06:54:51 example kernel: em2: link state changed to UP
Jun 13 06:59:22 example kernel: em2: watchdog timeout -- resetting
Jun 13 06:59:22 example kernel: em2: link state changed to DOWN
Jun 13 06:59:25 example kernel: em2: link state changed to UP




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4853055C.2030303>