From owner-freebsd-hackers  Mon Nov 30 07:08:57 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA06280
          for freebsd-hackers-outgoing; Mon, 30 Nov 1998 07:08:57 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06274
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 30 Nov 1998 07:08:54 -0800 (PST)
          (envelope-from cshenton@uucom.com)
Received: (from cshenton@localhost)
	by samizdat.uucom.com (8.9.1/8.9.0) id KAA18603;
	Mon, 30 Nov 1998 10:08:31 -0500
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: 2.2.7 on K6/2, SCSI ncr0 hangs/aborts at boot, then recovers
References: <199811260524.VAA00686@dingo.cdrom.com>
From: Chris Shenton <cshenton@uucom.com>
Date: 30 Nov 1998 10:08:31 -0500
In-Reply-To: Mike Smith's message of Wed, 25 Nov 1998 21:24:31 -0800
Message-ID: <86yaotgqvk.fsf@samizdat.uucom.com>
Lines: 12
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith <mike@smith.net.au> writes:

> When you say "in a sketchy way", do you mean that the system is working 
> OK from this point on, or are there other problems?

Yeah, it seems to be fine after it completes the boot process.

> Different code talking to the device; the bootstrap uses the BIOS, 
> while the kernel uses its own driver.  It looks like the NCR part is 
> left in a funny state that takes a restart (several?) to recover from.

Is there anything I can/should enable to track this down? 

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