From owner-freebsd-questions Mon Sep 11 13: 9:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DC9A837B43C for ; Mon, 11 Sep 2000 13:09:12 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8BK9Cm28655; Mon, 11 Sep 2000 13:09:12 -0700 (PDT) Date: Mon, 11 Sep 2000 13:09:12 -0700 From: Alfred Perlstein To: David Kirchner Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Strange procfs bug(?) 3.2-RELEASE Message-ID: <20000911130912.N12231@fw.wintelcom.net> References: <20000911120640.J12231@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from dpk@parodius.com on Mon, Sep 11, 2000 at 12:19:25PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Kirchner [000911 12:19] wrote: > > > Yes, there's a problem with procfs in 3.2 when you stress it heavily > > like that, my suggestion is to get 4-stable running, or at least try > > to get 3.5.1 up and running, but I'm unsure if it's fixed in 3.5.1. > > > > -Alfred > > Is this related? : > > "Don't call calcru() on a swapped-out process. calcru() access p_stats, > which is in U-area." > > That's from CVSweb at file procfs_status.c, revision 1.14 I'm not really a procfs guru, I only know about your reported problem, I've never heard of that message though. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message