From owner-freebsd-net  Wed May 31  1: 0:12 2000
Delivered-To: freebsd-net@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 58C6A37B76E; Wed, 31 May 2000 01:00:04 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id JAA91324;
	Wed, 31 May 2000 09:59:41 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200005310759.JAA91324@freebsd.dk>
Subject: Re: system hangs... (fwd)
In-Reply-To: <Pine.GSO.4.10.10005311311580.14865-100000@sund6.sasi.com> from "G.B.Naidu" at "May 31, 2000 01:13:40 pm"
To: gbnaidu@sasi.com (G.B.Naidu)
Date: Wed, 31 May 2000 09:59:41 +0200 (CEST)
Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It seems G.B.Naidu wrote:
> 
> I have posted this earlier. I didnt get any reply about system hangs.
> Please some body help me out to track down these hangs. Questions are
> below.

Have you tried putting DDB into the kernel, and tried to
hit ALT+CTRL+ESC to go into the debugger on the hang ?

Printf is a good tool here, sprinkle your source with
printf's so you can see how far you get, and what 
essential values are getting used.

Another possibility is to attach 8 LED's to a printer
port, those you can then turn on/off at will by a simple
outb statement. I use a 2*40 char LCD display connected
this way sometimes, that gives me a history of 80 values,
so I can se the exact sequence of events that let me to 
the problem at hand..

-Søren


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