From owner-freebsd-current Tue May 21 06:37:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA25244 for current-outgoing; Tue, 21 May 1996 06:37:18 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA25238 for ; Tue, 21 May 1996 06:37:15 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id IAA08833; Tue, 21 May 1996 08:37:06 -0500 (EST) From: "John S. Dyson" Message-Id: <199605211337.IAA08833@dyson.iquest.net> Subject: Re: Possible problem with new VM code? To: sysseh@devetir.qld.gov.au (Stephen Hocking) Date: Tue, 21 May 1996 08:37:06 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <199605210520.FAA21386@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at May 21, 96 03:20:42 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I actually managed to provoke a crash with DDB at the ready while the system > was under heavy load! This is on different hardware (486/66, 16Mb with IDE, > the old one was 486/66, 8Mb, 1542B + barracuda) & without the suggested > alteration of splvm to be the same as splhigh) Mind you, it took two make > worlds & running the quake binary to do it. The backtrace is as follows (note > I've compiled the kernel with -O2 -m486) - > > panic: vm_page_activate: already active > There is a syndrome that everyone seems to be tripping over. It isn't spl related, and will be working on it tonight. John