Date: Tue, 6 Jun 1995 13:15:17 +0100 (BST) From: Doug Rabson <dfr@render.com> To: "Jordan K. Hubbard" <jkh@freefall.cdrom.com> Cc: Frank Durda IV <uhclem%nemesis@fw.ast.com>, jgreco@brasil.moneng.mei.com, hackers@FreeBSD.org, bugs@FreeBSD.org Subject: Re: 2.0.5-A: Very disheartening? Message-ID: <Pine.BSF.3.91.950606131357.1240A-100000@minnow.render.com> In-Reply-To: <28172.802415540@freefall.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Jun 1995, Jordan K. Hubbard wrote: > > Once 2.0.5-Alpha is installed and running on a non-compressed kernel, I can > > put the cache back in (or enable it) and everything still works, even with > > memory amounts that would panic or hang with the cache present. > > Just FYI, > > David, Poul and I (mostly holding coats and looking anxious) are all > looking into potential badness in the kzip/MFS code which could > explain this. If it comes to it, we may very well fall back to a 2 > floppy install! We're trying to look at all the options.. > > Something one way or the other will probably be decided in the next > 2-3 days. > > If those actually seeing the problem would care at all to play with > kzip a little and see if they can't perhaps narrow the failure mode > down, I'd be more than pleased! It's a lot easier to frown at kernel > printfs() meaninfully when you can actually reproduce the failure > locally! :-) I am pretty sure that my problem was nothing to do with kzip since the install worked fine. I have just build a new kernel from the 2.0.5A sources so I will see how that flies. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.950606131357.1240A-100000>