From owner-freebsd-hackers Sun Feb 15 14:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05111 for freebsd-hackers-outgoing; Sun, 15 Feb 1998 14:43:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05100 for ; Sun, 15 Feb 1998 14:43:04 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA13751; Sun, 15 Feb 1998 15:09:00 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd013720; Sun Feb 15 15:08:53 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id PAA04157; Sun, 15 Feb 1998 15:08:49 -0700 (MST) From: Terry Lambert Message-Id: <199802152208.PAA04157@usr01.primenet.com> Subject: Re: VM messed: vm_page_free panic problem To: sthaug@nethelp.no Date: Sun, 15 Feb 1998 22:08:49 +0000 (GMT) Cc: tlambert@primenet.com, roberto@keltia.freenix.fr, hackers@FreeBSD.ORG In-Reply-To: <4541.887579521@verdi.nethelp.no> from "sthaug@nethelp.no" at Feb 15, 98 10:52:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ah. Compression. Disable your internal and external cache for the > > time you are booting, and see if it fixes it. Also, do you have 48M? > > If so, remove 16M for the install. > > Many other people (myself included) are seeing the exact same problem. > I had it on a machine with 64 M. Also, I highly doubt that we're all > having problems with our floppies, caches etc. What about cache interaction and the decompression algortihm on the disk? Are you using a processor that writes back or doesn't write back the cache as a result of changes in the instruction stream? Older processors do not write back. Newer processors do. This problem could easily be specific to newer processors and/or newer MMU chipsets (for example, on my "old" P90's and my Neptune chipset, I do *not* see this problem). We need more specific information about the hardware in the damage path, and not just all the specific information in the world (ie: 4000 lines of boot messages times 20 people is too much to wade through). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message