From owner-freebsd-net Sat Jun 15 19:53:52 2002 Delivered-To: freebsd-net@freebsd.org Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [211.176.62.31]) by hub.freebsd.org (Postfix) with ESMTP id 45C8A37B403 for ; Sat, 15 Jun 2002 19:53:47 -0700 (PDT) Received: from gradius.wdb.co.kr (daemon [211.176.62.31]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id 45A518F625 for ; Sun, 16 Jun 2002 11:53:45 +0900 (KST) Received: from localhost (localhost [127.0.0.1]) by gradius.wdb.co.kr (8.12.3/8.12.3) with ESMTP id g5G2rgii015998 for ; Sun, 16 Jun 2002 11:53:43 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) Date: Sun, 16 Jun 2002 11:53:42 +0900 (KST) Message-Id: <20020616.115342.74737454.cjh@kr.FreeBSD.org> To: freebsd-net@freebsd.org Subject: em0 watchdog timeout in 4.6R From: CHOI Junho Organization: Korea FreeBSD Users Gruop X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 3.0.55 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am maintaining a large-volume HTTP server. It is with one em0 gigabit NIC, and running apache(or thttpd) for users to download relatively big(>200k) files. I started this service using 4.5R. It shows about 500Mbit/sec performance(the server is Pentium III 1G, 1G RAM, 36G SCSI HDD). Server load was very high(>200) but I heard it's characteristic of apache server and I decided to upgrade to recent system and use thttpd instead of apache. 2 days ago I updated the system to 4.6-RELEASE. Whether or not using apache or thttpd, under some traffic(about >150Mbit/sec), it shows "watchdog timeout" repeatedly: Jun 16 11:36:18 gigatest /kernel: em0: Link is Down Jun 16 11:36:18 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:40:49 gigatest /kernel: em0: watchdog timeout -- resetting Jun 16 11:40:51 gigatest /kernel: em0: Link is Down Jun 16 11:40:51 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:40:51 gigatest /kernel: em0: Link is Down Jun 16 11:40:51 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:44:23 gigatest /kernel: em0: watchdog timeout -- resetting Jun 16 11:44:24 gigatest /kernel: em0: Link is Down Jun 16 11:44:24 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:50:28 gigatest /kernel: em0: watchdog timeout -- resetting Jun 16 11:50:29 gigatest /kernel: em0: Link is Down Jun 16 11:50:29 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:50:30 gigatest /kernel: em0: Link is Down Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex Jun 16 11:50:30 gigatest /kernel: em0: Link is Down Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps FullDuplex Jun 16 11:50:30 gigatest /kernel: em0: Link is Down Jun 16 11:50:30 gigatest /kernel: em0: Link is up 1000 Mbps Full Duplex I updated em0 driver to 1.3.8 from Intel webpage, but it no helps. Can you suggest some advice? If not, I have to back to 4.5R-p5. -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now] [while sleeping] Korea FreeBSD Users Group Web Data Bank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message