From owner-freebsd-net@FreeBSD.ORG Tue Nov 14 18:21:59 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 9C1E816A403; Tue, 14 Nov 2006 18:21:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA66F43D75; Tue, 14 Nov 2006 18:21:58 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 600DC46D8F; Tue, 14 Nov 2006 13:21:58 -0500 (EST) Date: Tue, 14 Nov 2006 18:21:58 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Randy Bush In-Reply-To: <17753.64161.965166.601002@roam.psg.com> Message-ID: <20061114181823.K87081@fledge.watson.org> References: <17752.41644.706579.902238@roam.psg.com> <17753.64161.965166.601002@roam.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, FreeBSD Current Subject: Re: fxp going quiescent in current X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 18:21:59 -0000 On Tue, 14 Nov 2006, Randy Bush wrote: >> FreeBSD rip.psg.com 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Sat Nov 11 19:18:23 GMT 2006 root@rip.psg.com:/usr/obj/usr/src/sys/RIP i386 >> >> and for the last four or five days, fxp0 goes dead. it shows up >> and active, but no packets move. >> >> down/up does not help. only way out has been reboot. >> >> suggestions on how to debug? > > this is killing me. noc woke me up twice in night to reboot the sucker. > any clues? Do you have serial console access to the box? The usual questions read: (1) When it's "dead", do interrupts still fire for the interface when packets go near by? See vmstat -i. (2) Does the driver think the link is still negotiated? What are the interface flags set to? See ifconfig. (3) When you run tcpdump on the interace, does it see packets from the outside world? (4) If you ping out the interface, does tcpdump see packets? Do you get ENOBUFS? Have ping send at least 256 packets. Do you get errors? Send to the broadcast address so that arp doesn't need to be working to transmit. (5) What does netstat -m show? (6) Any unusual dmesg output? In particular, any mention of fxp state changes or watchdogs firing? (7) Does lowering the interface, waiting ten seconds, then raising it help? Notice that these are all much easier if you have a serial console. If not, you might want to do the above using cron and a temporary file followed by a reboot. :-) Robert N M Watson Computer Laboratory University of Cambridge