From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 5 19:33:02 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB4221065676; Fri, 5 Dec 2008 19:33:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 82BCB8FC2D; Fri, 5 Dec 2008 19:33:02 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (blacklion.dialup.corbina.ru [89.179.122.169]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id CFD6713DF5D; Fri, 5 Dec 2008 22:21:19 +0300 (MSK) Date: Fri, 5 Dec 2008 22:13:24 +0300 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <785999360.20081205221324@serebryakov.spb.ru> To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: jfv@FreeBSD.org, freebsdnic@mailbox.intel.com Subject: em0: watchdog timeout -- resetting X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2008 19:33:02 -0000 Hello, . System: FreeBSD xxx.xxx.xx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Dec 5 20:= 37:31 MSK 2008 lev@xxx.xxx.xx:/usr/obj/usr/src/sys/BLOB amd64 Hardware: % dmesg | grep em0 em0: port 0xe880-0xe89f mem 0x= fea40000-0xfea5ffff,0xfea7a000-0xfea7afff irq 20 at device 25.0 on pci0 em0: [FILTER] em0: Ethernet address: 00:1e:8c:75:03:0d % pciconf -lv | grep em0@pci0:0:25:0: class=3D0x020000 card=3D0x82681043 chip=3D0x10bd808= 6 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82566DM-2 Gigabit Network Connection' class =3D network subclass =3D ethernet % ifconfig em0 em0: flags=3D8843 metric 0 mtu 9014 options=3D19b ether 00:1e:8c:75:03:0d inet 192.168.134.3 netmask 0xffffff00 broadcast 192.168.134.255 media: Ethernet autoselect (1000baseTX ) status: active % Hardware is ASUS P5E-VM DO motherboard with integrated controller. Network is connected to HP ProCurce 1400-8G gigabit switch. I'm getting "em0: watchdog timeout -- resetting" (and all connections are lost!) very often. If here are network load it could be every 5 minutes sometimes... For example: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dec 5 22:01:39 blob kernel: em0: watchdog timeout -- resetting Dec 5 22:01:39 blob kernel: em0: link state changed to DOWN Dec 5 22:01:42 blob kernel: em0: link state changed to UP Dec 5 22:01:56 blob kernel: em0: watchdog timeout -- resetting Dec 5 22:01:56 blob kernel: em0: link state changed to DOWN Dec 5 22:01:59 blob kernel: em0: link state changed to UP Dec 5 22:02:01 blob kernel: em0: link state changed to DOWN Dec 5 22:02:03 blob kernel: em0: link state changed to UP Dec 5 22:06:07 blob kernel: em0: watchdog timeout -- resetting Dec 5 22:06:07 blob kernel: em0: link state changed to DOWN Dec 5 22:06:09 blob kernel: em0: link state changed to UP Dec 5 22:07:18 blob kernel: em0: watchdog timeout -- resetting Dec 5 22:07:18 blob kernel: em0: link state changed to DOWN Dec 5 22:07:24 blob kernel: em0: link state changed to UP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I could provide any additional information. --=20 // Black Lion AKA Lev Serebryakov