From owner-freebsd-stable@FreeBSD.ORG Wed Oct 4 06:13:42 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 B836716A407 for ; Wed, 4 Oct 2006 06:13:42 +0000 (UTC) (envelope-from John.Marshall@riverwillow.com.au) Received: from mail2.riverwillow.net.au (ns2.riverwillow.net.au [203.58.93.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C57743D76 for ; Wed, 4 Oct 2006 06:13:41 +0000 (GMT) (envelope-from John.Marshall@riverwillow.com.au) Received: from rwmail.mby.riverwillow.net.au (rwsrv06.rw2.riverwillow.net.au [172.25.25.16]) by mail2.riverwillow.net.au (8.13.8/8.13.8) with ESMTP id k946Dejo057614; Wed, 4 Oct 2006 16:13:40 +1000 (AEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 4 Oct 2006 16:13:40 +1000 Message-ID: <9F7B653A50CF3D45A92C05401046239B0E0C28@rwsrv06.rw2.riverwillow.net.au> In-Reply-To: <20061004051857.GA58194@icarus.home.lan> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Watchdog Timeout - bge devices thread-index: AcbndVApimh2nOoRQEabxXC4YEU9kAABRwqw From: "John Marshall" To: "Jeremy Chadwick" , X-Spam-Status: No, score=-18.7 required=4.0 tests=ALL_TRUSTED,SPF_FAIL autolearn=disabled version=3.1.5 X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on mail2.riverwillow.net.au Cc: 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 06:13:42 -0000 Jeremy Chadwick wrote: > > As far as SCHED_ULE goes, if you have issues with it, use SCHED_4BSD. >=20 > Now, about watchdog timeouts in general -- there's a pending issue > which is still under investigation. Please see this thread: >=20 That was the "em" thread to which I referred in my original post. That thread seemed to me to be settling down to symptoms induced by interrupt sharing and the presence of USB device drivers - nothing ULE-specific. I don't have any of those other ingredients present and can only induce the symptoms with SCHED_ULE configured - and only on the on-board Ethernet devices (bge) not the PCI cards (fxp). Since I don't think there's anything else useful I can add to that discussion, I'll just revert to exclusive use of SCHED_4BSD, sit back and keep reading. Thanks. John Marshall.