From owner-freebsd-current Thu Feb 1 11:26:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id C281A37B65D for ; Thu, 1 Feb 2001 11:26:39 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14OPNM-0001Fw-00; Thu, 01 Feb 2001 21:26:36 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id VAA15959; Thu, 1 Feb 2001 21:26:35 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 15927; Thu Feb 1 21:26:31 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 14OPNI-000AOa-00; Thu, 01 Feb 2001 21:26:32 +0200 To: Cejka Rudolf Cc: freebsd-current@freebsd.org Subject: Re: Does task scheduler work correctly? (... nice bug fix) In-reply-to: Your message of "Thu, 01 Feb 2001 20:14:13 +0100." <20010201201413.A55503@dcse.fee.vutbr.cz> Date: Thu, 01 Feb 2001 21:26:32 +0200 Message-ID: <39963.981055592@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Feb 2001 20:14:13 +0100, Cejka Rudolf wrote: > Ok, scheduler in -current is not broken. But I'm afraid that in -stable > it is - can (niced) process cause a lock of machine?. You should really talk to Brian Feldman . The last time I chatted to him about this, I was left with the impression that priority-handling in -stable could, in certain corner cases, result in deadlocks. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message