From owner-freebsd-current@FreeBSD.ORG Thu Apr 27 23:00:37 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 B2DC816A432; Thu, 27 Apr 2006 23:00:35 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19B8C43D46; Thu, 27 Apr 2006 23:00:32 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.4/8.13.3) with ESMTP id k3RN0V4n067087; Thu, 27 Apr 2006 16:00:31 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.13.4/8.13.3/Submit) id k3RN0UwP067086; Thu, 27 Apr 2006 16:00:30 -0700 (PDT) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Thu, 27 Apr 2006 16:00:30 -0700 From: "David G. Lawrence" To: John Baldwin Message-ID: <20060427230030.GU96684@tnn.dglawrence.com> References: <20060328044432.152CD45047@ptavv.es.net> <4428D0EE.6080603@FreeBSD.org> <20060328063930.GC12815@tnn.dglawrence.com> <200604271730.49268.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604271730.49268.jhb@freebsd.org> Cc: Bachilo Dmitry , freebsd-current@freebsd.org, Sergey Matveychuk Subject: Re: nve0: device timeout (1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 27 Apr 2006 23:00:37 -0000 > > I have a work-around patch for the problem that I've attached to this > > email. It simply disables the watchdog. A real fix would involve accounting > > for the outstanding transmit buffers differently (or perhaps not at all - > > e.g. always attempt to call the nvidia-supplied code and if a queue-full > > error occurs, then wait for an interrupt before trying to queue more > > transmit packets). > > What about the patch just posted to amd64@? It looks like a patch for > this issue. It changes the watchdog() routine to detect this condition > and if it happens exit the routine early without emitting a printf or > resetting the chip. Yeah, I saw the patch. It seems like a reasonable fix to me - maybe just a little kludgy, but it has better performance than a fully 'correct' fix. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.