From owner-freebsd-net@FreeBSD.ORG Fri Sep 24 11:58:06 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12AF116A4D1 for ; Fri, 24 Sep 2004 11:58:06 +0000 (GMT) Received: from mxb.rambler.ru (mxb.rambler.ru [81.19.66.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8995C43D45 for ; Fri, 24 Sep 2004 11:58:05 +0000 (GMT) (envelope-from pij@rambler.ru) Received: from mail5.rambler.ru (mail5.rambler.ru [81.19.66.7]) by mxb.rambler.ru (Postfix) with ESMTP id 3672884498 for ; Fri, 24 Sep 2004 15:58:03 +0400 (MSD) Received: from [81.19.66.146] (account pij@rambler.ru) by mail5.rambler.ru (CommuniGate Pro WebUser 4.2) with HTTP id 74855704 for freebsd-net@freebsd.org; Fri, 24 Sep 2004 15:58:03 +0400 From: "Pavel V.Zheltobryukhov" To: freebsd-net@freebsd.org X-Mailer: CommuniGate Pro WebUser Interface v.4.2 Date: Fri, 24 Sep 2004 15:58:03 +0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R"; format="flowed" Content-Transfer-Encoding: 8bit Subject: Intel PRO/1000 CT (82547EI) - em0: watchdog timeout X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 11:58:06 -0000 I have Intel 7210 Server Board with Intel PRO/1000 CT (82547EI) on-board. This NIC work fine under Win2K, but then I boot FreeBSD 5.2.1 I've got a message on console: em0: Link up 100Mbit full duplex and boot process suspended at this moment. After approx. 1 minute next messages appear em0: Watchdog timeout -- resetting em0: Link up 100Mbit full duplex em0: Watchdog timeout -- resetting I send Ctrl+C and boot process was continued. But network card doesn't work. I check cable - it's good. I can't send any ping packet to other computers. I tried other transmit modes - I switch NIC to 10Mbit half duplex and 10Mbit full duplex via ifconfig options. No result. What is a problem? Bad driver? That is not a card problem, because (as I wrote above) it work in Windows.