From owner-freebsd-current Sun Jan 11 16:30:34 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA24083 for current-outgoing; Sun, 11 Jan 1998 16:30:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA24064 for ; Sun, 11 Jan 1998 16:30:21 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA00418; Sun, 11 Jan 1998 19:30:04 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199801120030.TAA00418@dyson.iquest.net> Subject: Re: VM breakage in yesterday's -current? In-Reply-To: <19980112101448.06484@lemis.com> from Greg Lehey at "Jan 12, 98 10:14:48 am" To: grog@lemis.com (Greg Lehey) Date: Sun, 11 Jan 1998 19:30:04 -0500 (EST) Cc: FreeBSD-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey said: > I built a new kernel on one of my machines (razzia) yesterday, and > since then I've been getting hanging processes. This is quite > specific: one process (xtset, which sets an xterm title bar) hangs > waiting at vmpfw. It's NFS mounted, so possibly there's an NFS > problem in there, but it's hard to be sure. > > Any ideas? I know there's some VM problems at the moment. I'll keep > the kernel and try to find more details if anybody wants me to. > If you can, please try the new code that I am about to commit. I'll be able to make better use of any bug info given that code. -- 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.