From owner-freebsd-questions@FreeBSD.ORG Tue Jul 1 01:39:49 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF8B537B401 for ; Tue, 1 Jul 2003 01:39:49 -0700 (PDT) Received: from fepB.post.tele.dk (fepB.post.tele.dk [195.41.46.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9747344005 for ; Tue, 1 Jul 2003 01:39:48 -0700 (PDT) (envelope-from flemming@froekjaer.org) Received: from froekjaer.org ([62.242.2.70]) by fepB.post.tele.dk (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030701083945.ODHG17611.fepB.post.tele.dk@froekjaer.org> for ; Tue, 1 Jul 2003 10:39:45 +0200 Message-ID: <3F0156A0.6070309@froekjaer.org> Date: Tue, 01 Jul 2003 10:38:40 +0100 From: =?ISO-8859-1?Q?Flemming_Fr=F8kj=E6r?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Intel Gigabit net resetting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2003 08:39:50 -0000 Hello, I tried a Intel PRO/1000 nic im my FreeBSD server, but the performance wah horrible. What could be wrong? In the logfile I found the following: Jun 27 00:10:22 gate3 /kernel: em2: mem 0xfe900000-0xfe91ffff irq 5 at device 8.0 on pci2 Jun 27 00:10:22 gate3 /kernel: em2: Speed:N/A Duplex:N/A Jun 27 00:18:03 gate3 /kernel: em2: mem 0xfe900000-0xfe91ffff irq 5 at device 8.0 on pci2 Jun 27 00:18:03 gate3 /kernel: em2: Speed:N/A Duplex:N/A Jun 27 01:22:22 gate3 /kernel: em2: Link is up 1000 Mbps Full Duplex Jun 27 01:22:26 gate3 /kernel: em2: watchdog timeout -- resetting Jun 27 01:46:19 gate3 /kernel: em2: watchdog timeout -- resetting Jun 27 01:50:34 gate3 /kernel: em2: watchdog timeout -- resetting Jun 27 16:00:00 gate3 /kernel: em2: watchdog timeout -- resetting Jun 27 17:00:02 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 00:00:29 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 00:01:00 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 11:00:28 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 11:03:19 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 11:07:42 gate3 /kernel: em2: watchdog timeout -- resetting Jun 28 23:58:21 gate3 /kernel: em2: watchdog timeout -- resetting Jun 29 00:00:31 gate3 /kernel: em2: watchdog timeout -- resetting Jun 29 00:02:23 gate3 /kernel: em2: watchdog timeout -- resetting Jun 29 23:58:13 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 00:00:41 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 00:01:38 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 11:20:56 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 18:54:26 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 18:56:34 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:02:24 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:02:57 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:38:21 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:38:40 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:38:45 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:51:43 gate3 /kernel: em2: watchdog timeout -- resetting Jun 30 19:54:57 gate3 /kernel: em2: mem 0xfe900000-0xfe91ffff irq 5 at device 8.0 on pci2 Jun 30 19:54:57 gate3 /kernel: em2: Speed:N/A Duplex:N/A Best regards Flemming Frøkjær