From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 18 19:30:04 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B7D5106564A for ; Thu, 18 Sep 2008 19:30: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 11AA88FC1F for ; Thu, 18 Sep 2008 19:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8IJU3RT061197 for ; Thu, 18 Sep 2008 19:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8IJU3vm061196; Thu, 18 Sep 2008 19:30:03 GMT (envelope-from gnats) Date: Thu, 18 Sep 2008 19:30:03 GMT Message-Id: <200809181930.m8IJU3vm061196@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: miks@skynet.lv X-Mailman-Approved-At: Thu, 18 Sep 2008 19:44:01 +0000 Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: miks@skynet.lv List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2008 19:30:04 -0000 The following reply was made to PR amd64/127451; it has been noted by GNATS. From: miks@skynet.lv To: bug-followup@FreeBSD.org, miks@skynet.lv Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core Date: Thu, 18 Sep 2008 22:22:56 +0300 to understand better, this happen once in 2-3 minutes: " last pid: 98618; load averages: 29.81, 17.28, 15.03 up 6+23:13:22 22:15:50 1234 processes:159 running, 986 sleeping, 64 zombie, 25 lock CPU states: 1.1% user, 0.0% nice, 98.8% system, 0.0% interrupt, 0.0% idle " before 3 sec in this situation there was only 1 process running and load average was around 1. is it somehow related with lockmgr?