From owner-freebsd-stable Mon May 10 18:20:15 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 ECBBB15EDC; Mon, 10 May 1999 18:20:07 -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 SAA00175; Mon, 10 May 1999 18:16:09 -0700 (PDT) Message-Id: <199905110116.SAA00175@implode.root.com> To: Cliff Skolnick Cc: freebsd-stable@FreeBSD.ORG, luoqi@FreeBSD.ORG Subject: Re: vm_fault deadlock and PR 8416 (was Re: Strange reboot saga ) In-reply-to: Your message of "Mon, 10 May 1999 17:22:50 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 10 May 1999 18:16:09 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >After removing the patch from my system, poof - deadlock. > >I did the ctl-printscrean thing, and everything looked ok. There were a >bunch of locks, shared, but I could not make much sense beyond the "ps" and >doing a trace which did not give me much info since I could not figure out >how to trace a specific process. :( > >Anyways this is a production email and dns system, so I can't futz with it >too much. I've added the patch in and expect my system will run again until >*I* take it down. Usually it locks up within 24 hours without the patch, >and it has run 4+ days with no lockup with the patch. After 4 days I took >the system down to remote the patch and add debugging to my kernel, monday >rolls around and poof - locked up. > >I would urge someone who has more of a clue about the locking issues to take >a look at this. There are two patches mentioned in PR 8416...which one are you using? -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