From owner-freebsd-bugs@FreeBSD.ORG Mon Aug 4 17:00:12 2008 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 285961065671 for ; Mon, 4 Aug 2008 17:00:12 +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 1BCF48FC17 for ; Mon, 4 Aug 2008 17:00:12 +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 m74H0BE7019188 for ; Mon, 4 Aug 2008 17:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m74H0BcY019187; Mon, 4 Aug 2008 17:00:11 GMT (envelope-from gnats) Date: Mon, 4 Aug 2008 17:00:11 GMT Message-Id: <200808041700.m74H0BcY019187@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: misc/126230: weird process cpu usage stats and weird load average X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 17:00:12 -0000 The following reply was made to PR misc/126230; it has been noted by GNATS. From: Kris Kennaway To: Jakub Jasinski Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/126230: weird process cpu usage stats and weird load average Date: Mon, 04 Aug 2008 18:59:15 +0200 Jakub Jasinski wrote: > No. > > I ran ktrace on the processes and ktrace.out was empty. > > Read my follow up message: I already had a lengthy conversation with > Remko about this. > > NONE of the processes were running. The non-zero TIME is nonsense as > well and only accumulated after rsync was left running. That would be a very strange situation indeed, requiring multiple things to go wrong in bizarre ways. The more likely explanation is that the processes are in fact running and being reported correctly. Kris