From owner-freebsd-net@FreeBSD.ORG Wed Oct 31 16:41:02 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6D2516A419; Wed, 31 Oct 2007 16:41:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 67ACF13C48D; Wed, 31 Oct 2007 16:41:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l9VGe2Sa005195; Wed, 31 Oct 2007 10:40:02 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4728AFCC.7020706@samsco.org> Date: Wed, 31 Oct 2007 10:39:40 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> In-Reply-To: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 31 Oct 2007 10:40:02 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:41:02 -0000 Jack Vogel wrote: > I have found that the FAST interrupt handling is implicated > in the watchdog resets that I have seen. > > What I plan to do is revert to the way 6.2 had things, meaning > that FAST interrupts will be available but defined off by default. > > I wanted to know if anyone has an issue with this. And more > importantly, I have personally not seen this problem on 7, but > I could set up #ifdef's in that driver to be the same way. > > What does everyone think? > > Jack Let's give it another couple of days to work out the real problem before we throw in the towel. Follow-ups in private... Scott