From owner-freebsd-hackers  Mon Mar 31 09:51:25 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA29587
          for hackers-outgoing; Mon, 31 Mar 1997 09:51:25 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29542
          for <freebsd-hackers@freebsd.org>; Mon, 31 Mar 1997 09:50:43 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA16780; Mon, 31 Mar 1997 12:50:06 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 31 Mar 1997 12:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id GAA10773; Mon, 31 Mar 1997 06:40:23 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id GAA15593; Mon, 31 Mar 1997 06:46:02 -0500 (EST)
Date: Mon, 31 Mar 1997 06:46:02 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199703311146.GAA15593@lakes.water.net>
To: ponds!radio-do.de!fn, ponds!freebsd.org!freebsd-hackers
Subject: Re: SCSI subsystem died
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> My system died this night after upgrading with source to 2.2.1-RELEASE.
> Previous system was 2.2-RELEASE.
> 
> The messages on the console:
> 
> sd0(ahc0:0:0): SCB 0x1 - timed out in dataout phase, SCSISIGI == 0x4
> SEQADDR == 0x125
> sd0(ahc0:0:0): SCB 0x0 - timed out while recovery phase in progress
> sd0(ahc0:0:0): SCB 0x2 - timed out while recovery phase in progress
> sd0(ahc0:0:0): SCB 0x3 - timed out while recovery phase in progress
> sd0(ahc0:0:0): SCB 0x1 - timed out while recovery phase in progress
> sd0(ahc0:0:0): SCB 0x1 - timed out in dataout phase, SCSISIGI == 0x4
> SEQADDR == 0x126
> sd0(ahc0:0:0): abort message in message buffer

 This is very similar to my problem with my aha2940 and the SCSI
tape drive I've reported.

 I'd bet when my particular (reproducible) problem is corrected; you're
will be as well...

	- Dave Rivers -

> 
> Here is a verbose boot message from the 2.2.1 kernel. After 3 hours
> uptime the machine was not reponding on the console,but yet pingable.
> 
> Any sugestions, what I can do?

 I believe someone is working on the problem... (I think it's Justin,
but I'm not sure...)


	- Dave Rivers -

> 
> Gru"s
> 	Frank
> 
>