From owner-freebsd-current  Sun Mar 31 02:58:03 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA18958
          for current-outgoing; Sun, 31 Mar 1996 02:58:03 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA18949
          Sun, 31 Mar 1996 02:58:00 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id CAA00635; Sun, 31 Mar 1996 02:57:57 -0800 (PST)
Date: Sun, 31 Mar 1996 02:57:57 -0800 (PST)
Message-Id: <199603311057.CAA00635@silvia.HIP.Berkeley.EDU>
To: gibbs@freefall.freebsd.org
CC: current@freefall.freebsd.org
In-reply-to: <199603311040.CAA00741@silvia.HIP.Berkeley.EDU> (asami@cs.berkeley.edu)
Subject: Re: aic7xxx driver and parity error problems
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * I'm afraid it still doesn't work here.  I get the same "SCSISIGI=0x0"
 * during fsck, and it later panicks with "timed out command times out
 * again" while trying to start portmap.

Also, the "disable parity checking" workaround failed here, as I got
"timed out in message out phase, SCSISIGI=0xe6" and stuff (I'm not
sure, I had to reset the machine while it was still scrolling).

This threw the SCSI system into a serious funk as the next three
reboots, from cold start, failed with a solid hang during the probe
from ahc0 (I've told you about this before).

It has come up now (with parity checking disabled), so I guess it (the
workaround) does work sometimes.

Satoshi