From owner-freebsd-stable@FreeBSD.ORG Thu Oct 19 21:18:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E1AA16A403 for ; Thu, 19 Oct 2006 21:18:15 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171D143D46 for ; Thu, 19 Oct 2006 21:18:14 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id t32so900135pyc for ; Thu, 19 Oct 2006 14:18:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NsynJuybjUcit0pfhZzG0YJCCLw+RcBf9y13Odb605ASBLlraePaMmLrPKpdXJkPsv8QE2GMbHr7l6Y7Nf1cR7W8ha6MMFbRTOWaSMvF+kRLvBH29E+j+S1ywUgx+oZ5DwVvFsEH31GJsfuzXsqthCt9MNfJtQhilOZVSv1myE0= Received: by 10.35.123.10 with SMTP id a10mr672681pyn; Thu, 19 Oct 2006 14:18:13 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Thu, 19 Oct 2006 14:18:13 -0700 (PDT) Message-ID: <2a41acea0610191418q6c6fac45xdd9ad824bd6cae2f@mail.gmail.com> Date: Thu, 19 Oct 2006 14:18:13 -0700 From: "Jack Vogel" To: freebsd-stable@freebsd.org In-Reply-To: <20061019190221.GH71000@droso.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com> <4537C126.5000207@FreeBSD.org> <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com> <20061019190221.GH71000@droso.net> Subject: Re: em network issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2006 21:18:15 -0000 The engineer in our test group has installed 6.2 BETA2 and attempted via a number of tests to reproduce this problem, the machine even shares the em interrupt with usb, and yet so far he has been unsuccessful. I have an Intel driver about to be released, it is close, but not identical to the 6.2 driver, I would very much like to know if it has this same problem. Any volunteers that have this problem willing to load this driver, which will be called 6.2.9 when we release it I believe, and tell me if you still have these watchdogs? BTW, 6.2.9 also has TSO that can be enabled but you need to install the kernel stack patch. I'd like it tested without TSO at least at first. Thanks for the help, Jack