From owner-freebsd-current@FreeBSD.ORG Thu Nov 17 18:58:59 2005 Return-Path: X-Original-To: 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 EE7D116A41F; Thu, 17 Nov 2005 18:58:59 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F0CC43D46; Thu, 17 Nov 2005 18:58:58 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAHIwX6G006066; Thu, 17 Nov 2005 10:58:33 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAHIwOoc006061; Thu, 17 Nov 2005 10:58:24 -0800 (PST) Date: Thu, 17 Nov 2005 10:58:24 -0800 (PST) From: Matthew Dillon Message-Id: <200511171858.jAHIwOoc006061@apollo.backplane.com> To: John Baldwin References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <20051117143322.lvz347pzkcg480co@netchild.homeip.net> <200511171135.53903.jhb@freebsd.org> Cc: alan bryan , Alexander Leidinger , freebsd-current@freebsd.org, FreeBSD current mailing list , "Bjoern A. Zeeb" Subject: Re: [PATCH] nve(4) locking cleanup 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, 17 Nov 2005 18:59:00 -0000 A side note on the work I did on nv (nve) for DragonFly. I spent a very, very long time trying to fix the watchdog problems. I was able to greatly reduce instances of the watchdog timeout, but it still occurs under heavy load. Even worse, I can wedge the hardware to the point where a reboot or soft power-down does not fix the problem! I have to physically unplug the power cable from the box to make the device work again. It only takes ~30 min - 3 hours of testing to get the ethernet into this hardware-wedged state. At this point I believe that the remaining problems are entirely within Nvidia's nvnet object module. I don't think there is anything we can do about it short of NVidia coming out with an update (which isn't likely). Now, linux *has* a native implementation of this driver that does not use the Nvidia module, and I have gotten reports that it does not suffer from the same problems. I think the only way to solve the watchdog problems that nv (nve) has is to throw it in the trash and do a fresh port from the native driver in the linux tree. -Matt