From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 12 19:15:03 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9765916A400 for ; Thu, 12 Jul 2007 19:15:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 3284C13C48C for ; Thu, 12 Jul 2007 19:15:02 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [212.17.141.53] (account mc467741@c2i.net HELO [10.150.81.62]) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 444735302; Thu, 12 Jul 2007 20:14:58 +0200 From: Hans Petter Selasky To: freebsd-hardware@freebsd.org Date: Thu, 12 Jul 2007 20:14:59 +0200 User-Agent: KMail/1.9.5 References: <20070712174409.GA18457@crosswinds.net> In-Reply-To: <20070712174409.GA18457@crosswinds.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200707122014.59844.hselasky@c2i.net> Cc: tony@crosswind.snet Subject: Re: keyboard + if_nfe oddity X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2007 19:15:03 -0000 On Thursday 12 July 2007 19:44, Tony Holmes wrote: > Okay, here's an odd one. > > I have an Asus M2NPV-VM board using the nfe driver from > http://www.f.csce.kyushu-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > Traffic is moderate (approx 7Mbps) and every couple of days, the > nfe device just stops talking to the outside world. I do see one > type of error in the logs: > > Jul 12 10:08:33 cwpro1 kernel: nfe0: watchdog timeout (missed Tx > interrupts) -- recovering Jul 12 10:09:04 cwpro1 kernel: nfe0: watchdog > timeout (missed Tx interrupts) -- recovering > > > The solution? > > Plug in a keyboard (PS2). As soon as ukbd is probed, up fires the > ethernet device and we're talking again. > > So, any ideas? This box is in production so debugging time/possbilities > are limited. Maybe the keyboard generates a missing interrupt for the NFE controller. Are you using 7-current ? I have a box and the built in nfe0 adapter does not work very well, unless I use 7-current! --HPS