From owner-freebsd-current Mon Feb 2 11:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24745 for current-outgoing; Mon, 2 Feb 1998 11:44:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24704 for ; Mon, 2 Feb 1998 11:44:02 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00727; Mon, 2 Feb 1998 14:43:46 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802021943.OAA00727@dyson.iquest.net> Subject: Re: Current and X11R6 Signal 11 In-Reply-To: <34D613E8.3C3D3522@mindspring.com> from Ron Bolin at "Feb 2, 98 01:43:52 pm" To: rlb@mindspring.com (Ron Bolin) Date: Mon, 2 Feb 1998 14:43:46 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Ron Bolin said: > I am back running current as of 1-31-98 cvsup. I am no longer > experiencing X server > signal 11 aborts. This is because I stopped the 2.11 version of > xscreensaver from running. > > I'll have to find out which screensaver program makes the server abort > and report back to > see if anyone else has experienced the problem. > It might be that the screensaver just barely pushes the pageout daemon into operation. There is a deadlock that I now have a traceback for, that will take more than 10mins, but less than 2Hrs to fix. I'll probably start working on it in a few hours. (It is an algorithmic problem, and not a wierd timing problem, so it should be relatively easy to fix.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.