Date: Tue, 21 Oct 1997 00:36:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Urge to apply the vn device hack even to 2.2.5 Message-ID: <19971021003621.XE33370@uriah.heep.sax.de> In-Reply-To: <199710202003.WAA06920@adv.IAEhv.nl>; from Arjan de Vet on Oct 20, 1997 22:03:28 %2B0200 References: <199710201615.KAA29216@rocky.mt.sri.com> <199710202003.WAA06920@adv.IAEhv.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
As Arjan de Vet wrote: > I've done a 'make release' for 2.2-stable at least 5 times last week and I > haven't seen the vn panics either (with 64MB of RAM). Only some ioctl > message, see below. I didn't have an occasion to run a full `make release' after applying Nate's fix within the short time remaining before 2.2.5 is due. However, i've tried to torture the vn device of such a kernel, and haven't seen any ill effect. So i think we are safe with it. Perhaps it's indeed that you've got too much RAM. I remember Mr. KATO telling something about a condition that the lockmgr panic happened whenever something (from the vn object) was about to be paged in or out. So my normal (-current) `make release' machine has 32 MB of RAM (and X11 running by the same time), perhaps that condition is simply more likely then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971021003621.XE33370>