From owner-freebsd-current@FreeBSD.ORG Tue Dec 23 06:32:20 2003 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 DF3DB16A4CE; Tue, 23 Dec 2003 06:32:20 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDEB843D2D; Tue, 23 Dec 2003 06:32:19 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id D63525C766; Tue, 23 Dec 2003 06:32:19 -0800 (PST) Date: Tue, 23 Dec 2003 06:32:19 -0800 From: Alfred Perlstein To: pdeuskar@freebsd.org Message-ID: <20031223143219.GP60229@elvis.mu.org> References: <20031223142334.GO60229@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031223142334.GO60229@elvis.mu.org> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Tue, 23 Dec 2003 11:55:22 -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: Tue, 23 Dec 2003 14:32:21 -0000 * 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 -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684