From owner-freebsd-hackers  Mon Apr 28 21:50:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA24432
          for hackers-outgoing; Mon, 28 Apr 1997 21:50:42 -0700 (PDT)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA24424
          for <freebsd-hackers@freefall.FreeBSD.org>; Mon, 28 Apr 1997 21:50:37 -0700 (PDT)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA18636; Tue, 29 Apr 1997 00:50:05 -0400
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 29 Apr 1997 00:50 EDT
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id UAA15329; Mon, 28 Apr 1997 20:25:44 -0400 (EDT)
Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id UAA05509; Mon, 28 Apr 1997 20:32:24 -0400 (EDT)
Date: Mon, 28 Apr 1997 20:32:24 -0400 (EDT)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199704290032.UAA05509@lakes.water.net>
To: ponds!plutotech.com!gibbs, ponds!lakes.water.net!rivers
Subject: Re: Aha2940 problems with 940722 snap.
Cc: ponds!freefall.cdrom.com!freebsd-hackers
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> >
> >Just to let everyone know.
> >
> >I continue to see aha 2940 problems with the boot/fixit floppies
> >from the 4/22/97 SNAP (releng22)
> 
> The last set of changes that could affect your problem were committed
> on 4/26/97.
> 
> >My particular problem is that at the end of the SCSI tape write or
> >read the machine locks up (with the characteristic SCSI bus resets,
> >as reported many times by several people...)
> 
> I still need all of the following information in order to help you.
> 
> 1) boot -v dmesg output
> 2) The complete listing of all error messages when the hang occurs
> 
> This should be done on a "current" system (either the 2.1, 2.2, or
> current branch will work) of course.

 Uh, err, umm... certainly; except that I do this with the boot/fixit floppies.

 Is there a way to grab the dmesg output???

 Also; I have to, of course; write down the messages that occur
during the hang... since they don't get logged.  Hopefully that's
not error prone.

 Finally - I'm happy to try the latest 2.2 GENERIC kernel; is there
somewhere I can grab one?  I could simply put that in place and do
a normal boot -v and grab the dmesg, etc... output.  Would that be
adequate?

 Oh - and one more thing - Thanks for working on this!

	- Dave Rivers -