Date: Thu, 11 Sep 2003 01:34:09 +0300 From: Tomi Vainio - Sun Finland <Tomi.Vainio@Sun.COM> To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Cc: freebsd-current@freebsd.org Subject: Re: ufs related panic with latest current Message-ID: <16223.42721.306814.982653@ultrahot.finland.sun.com> In-Reply-To: <xzpy8ww5lfd.fsf@dwp.des.no> 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> <xzpy8ww5lfd.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav writes: > > 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. > If you could just give instructions what you wanna get when system panics I might be able to persuade the other that we should crash our system once more. What scripts should we run continously until system panics? What you want to check with kdb after system panics? Tomppa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16223.42721.306814.982653>