From owner-freebsd-hackers  Tue Aug 29 15:16:28 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id PAA26492
          for hackers-outgoing; Tue, 29 Aug 1995 15:16:28 -0700
Received: from haven.ios.com (haven.ios.com [198.4.75.45])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id PAA26484
          for <hackers@freebsd.org>; Tue, 29 Aug 1995 15:16:25 -0700
Received: (from rashid@localhost) by haven.ios.com (8.6.11/8.6.9) id SAA27856 for hackers@freebsd.org; Tue, 29 Aug 1995 18:17:22 -0400
From: "Rashid Karimov." <rashid@haven.ios.com>
Message-Id: <199508292217.SAA27856@haven.ios.com>
Subject: Chasing the ghost (DDB usage tips).
To: hackers@freebsd.org
Date: Tue, 29 Aug 1995 18:17:22 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 792       
Sender: hackers-owner@freebsd.org
Precedence: bulk

		Hi there folx,


	Looks like the lockups continue on that ASUS P54Tp4
	motherboards. This time the PC is pretty cool ( I
	mean the temperature) , there is extra fan inside
	especially for those Barracuda HDs, but system still
	locks up .
	The console driver still works for a while after the 
	locking so I think I'll able to run the DDB and kinda
	figure out what causes the system to lock.

	So if any1 here can provide any tip on DDB usage - 
	that would be great. Man page is not too helpful 
	in this sense,

	for example , how can I find if the SCSI driver
	is fine and is not locked ? If it is locked - in which 
	routine and what parameters were passed to it ...
	How to find the processes waiting for the resources
	and find the reason for them to be in the wait state ?

	Rashid