From owner-freebsd-stable@FreeBSD.ORG Wed Oct 4 05:25:07 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 9FB5316A403 for ; Wed, 4 Oct 2006 05:25:07 +0000 (UTC) (envelope-from dg@dglawrence.com) Received: from downloadtech.com (dt2-sfo.downloadtech.net [66.220.3.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4068443D5D for ; Wed, 4 Oct 2006 05:25:07 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (c-24-21-220-242.hsd1.or.comcast.net [24.21.220.242]) by downloadtech.com (8.12.9p1/8.12.9) with ESMTP id k945P06C026302; Tue, 3 Oct 2006 22:25:01 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.8/8.13.6) with ESMTP id k945Ot3h024072; Tue, 3 Oct 2006 22:24:55 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.13.8/8.13.8/Submit) id k945OrvW024071; Tue, 3 Oct 2006 22:24:53 -0700 (PDT) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Tue, 3 Oct 2006 22:24:53 -0700 From: David G Lawrence To: Scott Long Message-ID: <20061004052453.GO17642@tnn.dglawrence.com> References: <9F7B653A50CF3D45A92C05401046239B0E0C27@rwsrv06.rw2.riverwillow.net.au> <45234418.7000205@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45234418.7000205@samsco.org> Cc: freebsd-stable@freebsd.org, John Marshall Subject: Re: Watchdog Timeout - bge devices 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: Wed, 04 Oct 2006 05:25:07 -0000 > Very interesting data point. I wonder if this accounts for some of the > inconsistency in the reporting from others. In any case, SCHED_ULE is > still considered to be highly experimental. Hopefully it will get some > more attention in the near future to bring it closer to production > quality. I'm not using SCHED_ULE on any of the machines that I'm seeing the timeout problem with em and fxp devices. I suspect the problem has to do with interrupt thread scheduling; maybe SCHED_ULE just somehow makes the problem worse? -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.