From owner-freebsd-current@FreeBSD.ORG  Wed Sep 10 15:34:16 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7DD6516A4BF
	for <freebsd-current@freebsd.org>;
	Wed, 10 Sep 2003 15:34:16 -0700 (PDT)
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A553E43FAF
	for <freebsd-current@freebsd.org>;
	Wed, 10 Sep 2003 15:34:14 -0700 (PDT)
	(envelope-from tomppa@finland.sun.com)
Received: from sunfin.Finland.Sun.COM ([129.159.101.10])
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h8AMYA17010912;
	Wed, 10 Sep 2003 15:34:11 -0700 (PDT)
Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87])
	ESMTP id h8AMYAcP015134;	Thu, 11 Sep 2003 01:34:10 +0300 (EEST)
Received: from ultrahot.Finland.Sun.COM (localhost [127.0.0.1])
	h8AMY9Lx023686;	Thu, 11 Sep 2003 01:34:09 +0300 (EEST)
Received: (from tomppa@localhost)h8AMY9HU023683;
	Thu, 11 Sep 2003 01:34:09 +0300 (EEST)
From: Tomi Vainio - Sun Finland <Tomi.Vainio@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <16223.42721.306814.982653@ultrahot.finland.sun.com>
Date: Thu, 11 Sep 2003 01:34:09 +0300
To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=)
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>
X-Mailer: VM 7.17 under 21.4 (patch 9) "Informed Management" XEmacs Lucid
cc: freebsd-current@freebsd.org
Subject: Re: ufs related panic with latest current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Tomi.Vainio@Sun.COM
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2003 22:34:16 -0000

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