From owner-freebsd-current@FreeBSD.ORG Tue May 13 02:09:35 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC4411065674 for ; Tue, 13 May 2008 02:09:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mx1.freebsd.org (Postfix) with ESMTP id 84AFF8FC16 for ; Tue, 13 May 2008 02:09:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3971044rvf.43 for ; Mon, 12 May 2008 19:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=ufyHORtmgSxRn1XhS4JxG5EH82Ok8T1ePsGGkzlKpgc=; b=TBXDpg5oWMihdzhRomi6avJ06Yae1rIeqQJTEH+EQsZycD9ogEpi+0iPjZO4cR0kIzVPRLn2aKXs69u0c25sI2ADFUhmZt9zGJNFZ/yGTzzh3lS126CcEp7AiT4RFAXT88FLDwS+2z6xYKMofu/LkM/cvUvvhkZRuyhxSQontho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=AlnuHeG+dY4gyiYM/zhlSt5hLNRoqQ19zFt/1pomOAVTTuDiCkyYq6uO9P9+vw0DOSl1LzetkVIlWhBM08p0ZTwmxGbIqc9bG+rP95Z6GTfM3bDbBd1tFN9NnFlw1ONnx8S/5SK1gvXFdSPo2O18s15xtRMfDX1uo8efKZcXuSA= Received: by 10.140.147.18 with SMTP id u18mr4005759rvd.202.1210644575106; Mon, 12 May 2008 19:09:35 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id l31sm11724084rvb.6.2008.05.12.19.09.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 19:09:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m4D29R5j033379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 May 2008 11:09:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m4D29R7O033378; Tue, 13 May 2008 11:09:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 13 May 2008 11:09:27 +0900 From: Pyun YongHyeon To: Pascal Hofstee Message-ID: <20080513020927.GD32942@cdnetworks.co.kr> References: <20080512181259.04a2f542@nebuchadnezzar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080512181259.04a2f542@nebuchadnezzar> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org, yongari@freebsd.org Subject: Re: nfe0 watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 02:09:35 -0000 On Mon, May 12, 2008 at 06:12:59PM +0200, Pascal Hofstee wrote: > Hi, > Hi, > I recently decided to switch my CURRNET from i386 over to amd64 and > have since noticed an occasional occurance of the following phenomenon: > > Every couple of days the nfe0 interface (nVidia nForce MCP55 Ethernet > Controller ... Vitesse VSC6801 PHY) enters a mode from which it simply > will not recover. > > When it happens the console keeps spewing out > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > When this happens i have to reboot to get the interface working again. > (I'll probably build another custom kernel soon and disable the nfe > driver so i can try if a kldunload/kldload cycle will do the trick). > Can you see link state change reports of nfe(4) in your dmesg file? If you find any entries related with nfe(4) please show them to me. It may have a couple of link UP/DOWN messages and watchdog timeouts. > Considering i have never observed this phenomenon when running the > exact same system with CURRENT/i386 i wonder if this problem may be > some sort of 64-bit issue. > Probably not. > Any ideas and/or solutions would be appreciated. > When you know nfe(4) is not working anymore, would you check Rx MAC is still able to see incoming packets by invoking tcpdump on nfe(4) interface? It would be even better I can see verbosed boot messages related with nfe(4). > With kind regards, > Pascal Hofstee > -- Regards, Pyun YongHyeon