From owner-freebsd-current@FreeBSD.ORG  Tue Jan 27 13:29:14 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6C60416A4CE
	for <current@freebsd.org>; Tue, 27 Jan 2004 13:29:14 -0800 (PST)
Received: from mail.teleri.net (teleri.net [216.193.194.32])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2A2D243D54
	for <current@freebsd.org>; Tue, 27 Jan 2004 13:29:00 -0800 (PST)
	(envelope-from wd@teleri.net)
Received: by mail.teleri.net (Postfix, from userid 501)
	id B937F1145E; Tue, 27 Jan 2004 13:28:08 -0800 (PST)
Date: Tue, 27 Jan 2004 15:28:08 -0600
From: Chip Norkus <wd@teleri.net>
To: current@freebsd.org
Message-ID: <20040127212808.GA39325@teleri.net>
References: <Pine.NEB.3.96L.1040127155447.47712A-100000@fledge.watson.org>
	<8563.1075237470@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8563.1075237470@critter.freebsd.dk>
User-Agent: Mutt/1.4.1i
Subject: Re: Processes blocked on ufs or getblk
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2004 21:29:14 -0000


Replying to both here ..

On Tue Jan 27, 2004; 10:04PM +0100 Poul-Henning Kamp propagated the following:
> In message <Pine.NEB.3.96L.1040127155447.47712A-100000@fledge.watson.org>, Robe
> rt Watson writes:
> 
> >There is interest in this bug, and a couple of people are running into it. 

Okay.  Sorry for being antsy.  I'd just been monitoring the lists/threads
on this issue and hadn't seen any replies from People In The Know.  Thanks
for the info!

> 
> Can we please keep track of which scheduler people are using ?
> 

For what it's worth: I hit this particular bug in both SCHED_4BSD and
SCHED_ULE.

[snip]
> 
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe    
> Never attribute to malice what can adequately be explained by incompetence.

-chip
--
personal: chip norkus; renaissance hacker;        wd@teleri.net
work:     systems engineer @ lunarpages, inc.;    chip@lunarpages.com
info:     finger wd@teleri.net for plan or keys;  http://telekinesis.org