From owner-freebsd-stable Mon May 10 13:31:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id F2EBC14DDF for ; Mon, 10 May 1999 13:31:45 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA07804; Mon, 10 May 1999 16:31:42 -0400 (EDT) Message-Id: <3.0.5.32.19990510163104.01a7b100@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 10 May 1999 16:31:04 -0400 To: Cliff Skolnick From: Mike Tancsa Subject: Re: vm_fault deadlock and PR 8416 (was Re: Strange reboot saga ) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19990510151933.017f1b90@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:17 PM 5/10/99 -0700, Cliff Skolnick wrote: > >It seems to have solved my deadlock problems. I'm running w/o it now, ready >to try to go into the debugger after the next lockup. I'm expecting it >within a few hours. You mean, find / -type f -exec grep whatever "{}" \; & find / -type f -exec grep whatever "{}" \; & does not lock up your system right away ? I can do it on a number of my 3.x systems here and it locks them right away. I never had to wait a few hours for it to happen. FreeBSD 3.1-STABLE #0: Fri May 7 06:54:06 EDT 1999 for example dies within seconds. Or do you mean you are running with the patche as opposed to without ? ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message