Date: Thu, 11 Sep 2003 00:27:18 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Tomi.Vainio@Sun.COM Cc: freebsd-current@freebsd.org Subject: Re: ufs related panic with latest current Message-ID: <xzpy8ww5lfd.fsf@dwp.des.no> In-Reply-To: <16223.37193.123878.704675@ultrahot.finland.sun.com> (Tomi Vainio's message of "Thu, 11 Sep 2003 00:02:01 %2B0300") References: <16222.8328.482125.571191@ultrahot.finland.sun.com> <16222.14948.423489.596523@ultrahot.finland.sun.com> <20030910112539.F53623@carver.gumbysoft.com> <16223.32410.556709.818592@ultrahot.finland.sun.com> <xzp7k4g75p9.fsf@dwp.des.no> <16223.35291.354753.437544@ultrahot.finland.sun.com> <xzp3cf474ga.fsf@dwp.des.no> <16223.37193.123878.704675@ultrahot.finland.sun.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tomi Vainio - Sun Finland <Tomi.Vainio@Sun.COM> writes: > Second trace didn't have anything to do with fs only fork system calls > there so your expanation sounds reasonable. We probably don't see this > problem again because system now has enough memory (256M). It would be really useful to know where the fault lies. We might even (God forbid!) figure out a way to fix it. You can easily force the system to boot with less than the full amount of memory by setting hw.physmem to e.g. "64m" in /boot/loader.conf or at the loader prompt. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpy8ww5lfd.fsf>