From owner-freebsd-stable Wed May 12 0:56:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 74F8615D07; Wed, 12 May 1999 00:56:32 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id AAA01361; Wed, 12 May 1999 00:55:29 -0700 (PDT) Message-Id: <199905120755.AAA01361@implode.root.com> To: Cliff Skolnick Cc: Mike Tancsa , freebsd-stable@FreeBSD.ORG, luoqi@FreeBSD.ORG, Matthew Dillon Subject: Re: vm_fault deadlock and PR 8416 ... NOT fixed! In-reply-to: Your message of "Tue, 11 May 1999 22:47:26 PDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 12 May 1999 00:55:29 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Well a few minutes ago my system went into deadlock - and this is with the >kern_lock.c dated 5/11. This patch is different than the one in 8416 that >solved my problem before. I'd say this the problem is still there. Time is very short for getting this fixed before the release deadline. I think Luoqi's patch that was in the PR was suseptible to a priority inversion problem and has risks associated with using it. The fix that Matt Dillion made for -current that I back-ported to -stable was an attempt to fix the problem while minimizing the side effects. If it doesn't fix the problem then we'll proceed with plan B which is probably to just go with Luoqi's fix or to possibly troubleshoot Matt's fix (but as I said, time is short). >Once again my server is useless, deadlocked. No panic, responding to pings, >no ability to do disk I/O or any VM related stuff. > >An unhappy freebsd user once again, Is this really necessary? It sure doesn't help the debugging process. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message