Date: Sun, 15 Feb 1998 22:08:49 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: sthaug@nethelp.no Cc: tlambert@primenet.com, roberto@keltia.freenix.fr, hackers@FreeBSD.ORG Subject: Re: VM messed: vm_page_free panic problem Message-ID: <199802152208.PAA04157@usr01.primenet.com> In-Reply-To: <4541.887579521@verdi.nethelp.no> from "sthaug@nethelp.no" at Feb 15, 98 10:52:01 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802152208.PAA04157>