From owner-freebsd-current@FreeBSD.ORG Wed Jan 7 09:52:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7AB916A4CE for ; Wed, 7 Jan 2004 09:52:06 -0800 (PST) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D09C043D1D for ; Wed, 7 Jan 2004 09:52:03 -0800 (PST) (envelope-from mayday@gmx.net) Received: (qmail 23474 invoked by uid 65534); 7 Jan 2004 17:52:02 -0000 Received: from p508A8AC4.dip0.t-ipconnect.de (EHLO 192.168.0.3) (80.138.138.196) by mail.gmx.net (mp012) with SMTP; 07 Jan 2004 18:52:02 +0100 X-Authenticated: #431110 From: Benjamin Sobotta To: Alfred Perlstein Date: Wed, 7 Jan 2004 18:53:20 +0000 User-Agent: KMail/1.5.4 References: <20031223142334.GO60229@elvis.mu.org> <20031223143219.GP60229@elvis.mu.org> In-Reply-To: <20031223143219.GP60229@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401071853.20201.mayday@gmx.net> X-Mailman-Approved-At: Wed, 07 Jan 2004 21:02:54 -0800 cc: current@freebsd.org Subject: Re: em0 watchdog timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 17:52:06 -0000 I know it's kinda late, but I also still have exactly the same problem. Apart from that 5.2 works perfectly fine! Any hints?? -Ben On Tuesday 23 December 2003 14:32, Alfred Perlstein wrote: > * Alfred Perlstein [031223 06:23] wrote: > > I have this... > > em0: port > > 0x1000-0x103f mem 0xec800000-0xec81ffff,0xec820000-0xec83ffff irq 20 at > > device 8.0 on pci0 > > > > I keep getting this... > > em0: Link is up 1000 Mbps Full Duplex > > em0: watchdog timeout -- resetting > > em0: Link is up 1000 Mbps Full Duplex > > em0: watchdog timeout -- resetting > > em0: Link is up 1000 Mbps Full Duplex > > em0: watchdog timeout -- resetting > > em0: Link is up 1000 Mbps Full Duplex > > em0: Link is up 1000 Mbps Full Duplex > > em0: watchdog timeout -- resetting > > em0: Link is up 1000 Mbps Full Duplex > > em0: watchdog timeout -- resetting > > > > And the card doesn't seem to want to play with my other FreeBSD. > > > > Could the reset function be tweaked to be a bit more agressive? > > > > Is there something I can do to diagnose this? > > also this: > > em0: Excessive collisions = 0 > em0: Symbol errors = 0 > em0: Sequence errors = 0 > em0: Defer count = 0 > em0: Missed Packets = 18809 > em0: Receive No Buffers = 1281 > em0: Receive length errors = 0 > em0: Receive errors = 0 > em0: Crc errors = 0 > em0: Alignment errors = 0 > em0: Carrier extension errors = 0 > em0: XON Rcvd = 0 > em0: XON Xmtd = 2266 > em0: XOFF Rcvd = 0 > em0: XOFF Xmtd = 21061 > em0: Good Packets Rcvd = 1063512 > em0: Good Packets Xmtd = 1310406 > em0: fifo workaround = 0, fifo_reset = 0 > em0: hw tdh = 0, hw tdt = 0 > em0: Num Tx descriptors avail = 256 > em0: Tx Descriptors not avail1 = 0 > em0: Tx Descriptors not avail2 = 0 > em0: Std mbuf failed = 0 > em0: Std mbuf cluster failed = 0 > em0: Driver dropped packets = 0