From owner-freebsd-stable Thu Oct 18 1:28: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.asplinux.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id BAE8437B401; Thu, 18 Oct 2001 01:27:56 -0700 (PDT) Received: from asplinux.ru (sashkin.asplinux.ru [192.168.1.108]) by relay.asplinux.ru (8.11.6/8.11.6) with ESMTP id f9I8Rr816697; Thu, 18 Oct 2001 12:27:54 +0400 Message-ID: <3BCE92F0.8090809@asplinux.ru> Date: Thu, 18 Oct 2001 12:29:36 +0400 From: Alex Levine Reply-To: sashkin@home.com User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010829 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Possible bug in scheduler. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD 4-stable. Suspect the same in FreeBSD-current. resetpriority() calls maybe_resched() at the end after updating p_usrpri based on changed p_estcpu. maybe_resched() uses curpriority_cmp to compare priorities of current and given process and this function ( curpriority_cmp ) uses p_priority which is unchanged yet - the new p_usrpri is not reflected to p_priority yet. I'd appreciate an answer from anybody who can assess this problem. Regards Alex Levine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message