From owner-freebsd-bugs Mon Jul 3 17: 0: 9 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7D7CC37C07A for ; Mon, 3 Jul 2000 17:00:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA67720; Mon, 3 Jul 2000 17:00:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 3 Jul 2000 17:00:04 -0700 (PDT) Message-Id: <200007040000.RAA67720@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Doug White Subject: Re: bin/19630: systat consumes 100% CPU stuck in read() loop Reply-To: Doug White Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/19630; it has been noted by GNATS. From: Doug White To: Sheldon Hearn Cc: dwhite@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/19630: systat consumes 100% CPU stuck in read() loop Date: Mon, 3 Jul 2000 16:55:39 -0700 (PDT) On Mon, 3 Jul 2000, Sheldon Hearn wrote: > > > On Sat, 01 Jul 2000 14:03:32 MST, dwhite@FreeBSD.ORG wrote: > > > >How-To-Repeat: > > Run systat -vm 2 and wait about a minute. > > I can't duplicate this in 5.0-CURRENT (as of 2000-06-29). Could you try > with a 4.0-STABLE to see whether the problem exists there also? Doesn't happen on a -STABLE sup'd this morning (12:30AM PDT). Doesn't do it on another 4.0-RELEASE box either, but it's not the same type of condition. The problematic machine may have memory issues, though... grr. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message