From owner-freebsd-arch@FreeBSD.ORG Thu Jul 26 11:17:55 2007 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED0A116A41A; Thu, 26 Jul 2007 11:17:55 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from fupp.net (totem.fix.no [80.91.36.20]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA5F13C457; Thu, 26 Jul 2007 11:17:55 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from localhost (totem.fix.no [80.91.36.20]) by fupp.net (Postfix) with ESMTP id BEA1C8D98E6; Thu, 26 Jul 2007 13:17:54 +0200 (CEST) Received: from fupp.net ([80.91.36.20]) by localhost (totem.fix.no [80.91.36.20]) (amavisd-new, port 10024) with LMTP id aRGVZu1zGxJq; Thu, 26 Jul 2007 13:17:54 +0200 (CEST) Received: by fupp.net (Postfix, from userid 1000) id 5FF3C8D989A; Thu, 26 Jul 2007 13:17:54 +0200 (CEST) Date: Thu, 26 Jul 2007 13:17:54 +0200 From: Anders Nordby To: Robert Watson Message-ID: <20070726111754.GA80207@fupp.net> References: <20070724110908.T83919@fledge.watson.org> <20070726102328.GA12293@fupp.net> <20070726105358.GA43979@rot26.obsecurity.org> <20070726120713.Q15979@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070726120713.Q15979@fledge.watson.org> X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.11 Cc: arch@FreeBSD.org, jkim@FreeBSD.org, Kris Kennaway Subject: Re: Removing NET_NEEDS_GIANT: first patch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2007 11:17:56 -0000 hI! On Thu, Jul 26, 2007 at 12:11:49PM +0100, Robert Watson wrote: > I agree with what Kris said, only more so. :-) By masking the bug using > debug.mpsafenet, whatever bug is the root of the problem isn't getting > fixed, and instead keeps going out in releases. This sounds like it's most > likely a driver bug, although I wouldn't rule out some sort of interrupt > problem. It looks like jkim might be someone to talk to about this (CC'd). Does any of you know how to find the cause of the watchdog timeout? My (poor) excuse for still using debug.mpsafenet is that the servers are in production, and that I "just" wanted them to work as stable as possible. Cheers, -- Anders.