From owner-freebsd-stable Tue May 11 6:47:42 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 BE3D314C8B; Tue, 11 May 1999 06:47:32 -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 JAA29762; Tue, 11 May 1999 09:47:24 -0400 (EDT) Message-Id: <3.0.5.32.19990511094641.00fd0310@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 11 May 1999 09:46:41 -0400 To: freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: vm_fault deadlock and PR 8416 ... looks fixed! Cc: luoqi@FreeBSD.ORG, dg@root.com In-Reply-To: <199905110335.UAA11597@cwsys.cwsent.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:35 PM 5/10/99 -0700, Cy Schubert - ITSD Open Systems Group wrote: >In message <199905110116.SAA00175@implode.root.com>, David Greenman >writes: >> >> There are two patches mentioned in PR 8416...which one are you using? Thanks to dg@root.com, and luoqi@freebsd.org for the fix to this issue!! I noticed the commits go through last night. I have updated my work machine and the problem that was triggered by the two finds indeed seems fixed! Now I can update my publically exposed (exposed at least to our customers) 3.x production machine and I can sleep easier! Did anyone ever say FreeBSD rocks! ;-) ---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