From owner-freebsd-current  Sat Nov  9 18:00:09 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA03770
          for current-outgoing; Sat, 9 Nov 1996 18:00:09 -0800 (PST)
Received: from watt.cae.uwm.edu (hench@watt.cae.uwm.edu [129.89.52.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA03761
          for <freebsd-current@freebsd.org>; Sat, 9 Nov 1996 18:00:05 -0800 (PST)
Received: (from hench@localhost) by watt.cae.uwm.edu (8.6.12/8.6.12) id TAA04624; Sat, 9 Nov 1996 19:59:57 -0600
From: Mike Hench <hench@cae.uwm.edu>
Message-Id: <199611100159.TAA04624@watt.cae.uwm.edu>
Subject: Re: 2.2 HARD lockup RFC b4 i try it again.
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Sat, 9 Nov 1996 19:59:56 -0600 (CST)
Cc: hench@cae.uwm.edu, freebsd-current@freebsd.org
In-Reply-To: <199611090422.UAA04924@freefall.freebsd.org> from "Justin T. Gibbs" at Nov 8, 96 08:21:59 pm
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> There were bugs in the aic7xxx driver that were fixed just after the
> tag went on the tree, but my pull-up request for those files has not
> been processed yet.  You should be testing -current, not the 2.2 tree
> yet anyway, as Poul has been requesting.
> Justin T. Gibbs
> ===========================================
>   FreeBSD: Turning PCs into workstations
> ===========================================
> 

it seemed that jkh pulled that stuff into 2.2 this morning so i tried that
again. same thing. i also tried a -current kernel (supped today)
no problems with build. locks up everytime it starts quotacheck. and once
during fsck and twice IMEDIATELY after the kernel loaded. this was on a
reset initiated boot as opposed to a complete powerdown.
im wondering if i have something else screwed, but the late august kernel
works fine. everytime. i tried relaxing my ram timings (just for grins) to
no avail. at this point i find it hard to believe that it is scsi
(software)  or aicxxxx related tho. probably some lovely scsi hardware 
crap. it's all internal and active terminated, but scsi does that
sometimes just to get on your nerves. :-(

thanks for your help tho.
mike hench
hench@cae.uwm.edu