From owner-freebsd-stable Tue Dec 30 10:25:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13400 for stable-outgoing; Tue, 30 Dec 1997 10:25:37 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA13382 for ; Tue, 30 Dec 1997 10:25:30 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xn6M3-00057z-00; Tue, 30 Dec 1997 10:25:27 -0800 Date: Tue, 30 Dec 1997 10:25:25 -0800 (PST) From: Tom To: The Hermit Hacker cc: freebsd-stable@freebsd.org Subject: Re: Nov 21st stable kernel panicking... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, The Hermit Hacker wrote: > I got another crash after upgrading the kernel, this time looking > like the following. I would suspect swap space, based on it being in the > vm_ code, except that I haven't added or removed any swap space in several > months: There were some VM bugs fixed shortly after 2.2.5.... Can you try a "make buildworld" on another machine, then "installworld" it on the troubled machine? I do this around here, as I have a half-dozen machines to upgrade, but it also has advantange of being quite a bit faster. An "installworld" only takes 30 minutes over ethernet. Tom