From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 17 19:20:04 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ABB9106566C for ; Thu, 17 Dec 2009 19:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C180E8FC0C for ; Thu, 17 Dec 2009 19:20:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBHJK3BZ097029 for ; Thu, 17 Dec 2009 19:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBHJK3x6097028; Thu, 17 Dec 2009 19:20:03 GMT (envelope-from gnats) Resent-Date: Thu, 17 Dec 2009 19:20:03 GMT Resent-Message-Id: <200912171920.nBHJK3x6097028@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Volodymyr Kostyrko Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEFCC106566B for ; Thu, 17 Dec 2009 19:19:57 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id CE8338FC1F for ; Thu, 17 Dec 2009 19:19:57 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nBHJJvHK094384 for ; Thu, 17 Dec 2009 19:19:57 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id nBHJJvCY094383; Thu, 17 Dec 2009 19:19:57 GMT (envelope-from nobody) Message-Id: <200912171919.nBHJJvCY094383@www.freebsd.org> Date: Thu, 17 Dec 2009 19:19:57 GMT From: Volodymyr Kostyrko To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/141721: (id|rt)prio priority resets when new thread is created X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 19:20:04 -0000 >Number: 141721 >Category: kern >Synopsis: (id|rt)prio priority resets when new thread is created >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Dec 17 19:20:03 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Volodymyr Kostyrko >Release: RELENG_8 >Organization: >Environment: FreeBSD limbo.lan 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Dec 17 12:42:39 EET 2009 arcade@limbo.lan:/usr/obj/usr/src/sys/MINIMAL_8 i386 >Description: I'm just curious about this one. I've got a big bunch mail and news on my home computer. On ZFS with compression my mail profile weights 250Mb. I prefer to use seamonkey. But sometimes after update seamonkey tries to compress mail folders which can be huge. With 20 threads seamonkey effectively blocks my computer from doing anything. The simple solution I tried was idling seamonkey for 1 level with idprio 1 -pid. But I was very surprised that one minute later top shows that seamonkey has normal priority. Checking top continuously I realiased that each time a new thread starts the priority resets to normal. Running idprio 1 -pid again sets priority and I can see that in top. But few moments later priority returns to normal again. >How-To-Repeat: Trying to run a program that creates threads with idprio and checking the status of it would suffice. >Fix: I'm not familiar with threading kernel code so I can't even imagine where the problem is. >Release-Note: >Audit-Trail: >Unformatted: