From owner-freebsd-stable Thu May 13 5:25:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 2ABB814BF9 for ; Thu, 13 May 1999 05:25:39 -0700 (PDT) (envelope-from netch@lucky.net) Received: (from netch@localhost) by burka.carrier.kiev.ua (8.Who.Cares/Guinness_Is_Better) id PAA03403; Thu, 13 May 1999 15:25:37 +0300 (EEST) (envelope-from netch) Date: Thu, 13 May 1999 15:25:37 +0300 (EEST) From: Valentin Nechayev Message-Id: <199905131225.PAA03403@burka.carrier.kiev.ua> To: freebsd-stable@freebsd.org Subject: Re: vm problem? In-Reply-To: Organization: Lucky Netch Incorporated User-Agent: tin/pre-1.4-980226 (UNIX) (FreeBSD/2.2.6-RELEASE (i386)) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IMHO this problem was solved by sys/vm/vm_fault.c patch in kern/8416 followup by Luoqi Chen, which was ported to -stable branch a few days ago. This problem also was described in kern/10226; I think it can be closed too. But, more careful tests are needed. Andy Farkas wrote: AF> Is anyone else seeing this? AF> On a 3.1-STABLE (Apr 14 1999) system, the following causes a vm lockup: AF> $ find / -type f -exec grep zztop "{}" \; & AF> $ find / -type f -exec grep zztop "{}" \; & AF> (ie. the same find command twice put in background... as a normal user) -- -- Valentin Nechayev netch@lucky.net II:LDXIII/MCMLXXII.CCC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message