Date: Mon, 18 Sep 2000 10:27:18 -0700 (PDT) From: David Kirchner <dpk@parodius.com> To: freebsd-current@freebsd.org Subject: Re: Strange procfs bug(?) 3.2-RELEASE Message-ID: <Pine.BSF.4.21.0009181026240.51752-100000@pentarou.parodius.com> In-Reply-To: <20000911130912.N12231@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Does anyone know if the patch indicated below was committed to fix this FreeBSD 3.2 bug? I can't upgrade to a later release yet, but if this patch is it, I can hack it in. On Mon, 11 Sep 2000, Alfred Perlstein wrote: > * David Kirchner <dpk@parodius.com> [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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009181026240.51752-100000>