From owner-freebsd-current  Sun Mar 31 02:40:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA17521
          for current-outgoing; Sun, 31 Mar 1996 02:40:37 -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 CAA17513
          Sun, 31 Mar 1996 02:40:30 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id CAA00741; Sun, 31 Mar 1996 02:40:28 -0800 (PST)
Date: Sun, 31 Mar 1996 02:40:28 -0800 (PST)
Message-Id: <199603311040.CAA00741@silvia.HIP.Berkeley.EDU>
To: gibbs@freefall.freebsd.org
CC: current@freefall.freebsd.org
In-reply-to: <199603310338.TAA12095@freefall.freebsd.org> (gibbs@freefall.freebsd.org)
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've just committed a new version of the aic7xxx driver that
 * I believe fixes the parity problems people were seeing.  If you
 * had parity problems, please try re-enabling parity checking in
 * SCSI-Select with the new driver and let me know.

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.

As you know, sd0 (Atlas 2GB narrow) + sd1 (Microp 4GB wide) + cd0
(Toshiba CDROM).  The SCSISIGI message comes during the fsck of sd0.

Satoshi