From owner-freebsd-current  Tue Jan 11 10:21:50 2000
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5AB2C14C3A
	for <freebsd-current@FreeBSD.ORG>; Tue, 11 Jan 2000 10:21:48 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id KAA39855;
	Tue, 11 Jan 2000 10:21:48 -0800 (PST)
	(envelope-from dillon)
Date: Tue, 11 Jan 2000 10:21:48 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200001111821.KAA39855@apollo.backplane.com>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Still system hangs, but different
References: <20000111131010.A317@relativity.student.utwente.nl> <20000111172846.A361@relativity.student.utwente.nl> <wpn1qcwk0x.fsf@heho.snv.jussieu.fr>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    Everyone, make sure you are using at least version 1.47 of
    ffs_softdep.c.

    If you manage (with the latest ffs_softdep.c ... 1.47) to get a lockup
    and your system still works well enough to run commands, and you were 
    smart enough to keep your kernel.debug lying around, then the following
    would be helpful:

	gdb -k kernel.debug /dev/mem
	proc (the pid of the stuck process)
	back
	proc (the pid of the next stuck process)
	back

    And a 'ps axl' output would be good too (trimmed if you know what to trim
    out).

    I think there may still a problem but I haven't been able to reproduce
    it yet.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message