Date: Tue, 6 Jun 1995 11:04:31 GMT From: Stephen Hocking <sysseh@devetir.qld.gov.au> To: bugs@FreeBSD.org Subject: Re: 2.0.5-A: Very disheartening? Message-ID: <199506061104.LAA15596@netfl15a.devetir.qld.gov.au>
next in thread | raw e-mail | index | archive | help
Might this not have something to do with unzipping something executable into memory and then failing to invalidate the cache entries for the memory you've just unzipped into? It sounds like a failure mode that you'd see with machines that have split I/D caches. I know it's easy to yell suggestions from the sidelines, but wouldn't it be a good idea to invalidate the cache after the image has been unzipped into memory? > >> 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! :-) > > Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506061104.LAA15596>