From owner-freebsd-bugs@FreeBSD.ORG Thu Jun 14 19:40:10 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 92C0D16A46C for ; Thu, 14 Jun 2007 19:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 4452B13C4B8 for ; Thu, 14 Jun 2007 19:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l5EJeAok020055 for ; Thu, 14 Jun 2007 19:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l5EJeADZ020054; Thu, 14 Jun 2007 19:40:10 GMT (envelope-from gnats) Date: Thu, 14 Jun 2007 19:40:10 GMT Message-Id: <200706141940.l5EJeADZ020054@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Gavin Atkinson Cc: Subject: Re: bin/60385: vmstat/iostat/top all fail to report CPU usage (still in 5.3R) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gavin Atkinson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2007 19:40:10 -0000 The following reply was made to PR bin/60385; it has been noted by GNATS. From: Gavin Atkinson To: jin@adsl-63-198-35-122.dsl.snfc21.pacbell.net Cc: Julien Gabel , Thomas Novin , Jeff Behl , Simon House , bug-followup@FreeBSD.org Subject: Re: bin/60385: vmstat/iostat/top all fail to report CPU usage (still in 5.3R) Date: Thu, 14 Jun 2007 20:31:51 +0100 (BST) [sent to everyone who was having problems in the audit-trail] Are you still able to reproduce this problem on more recent versions of FreeBSD? A significant number of changes have been made to the RTC code since this was submitted, and two changes in particular (including the one mentioned in the PR) may well have solved ot. So: Is anyone still seeing this issue? Thanks, Gavin