From owner-freebsd-hackers  Wed Jul  2 09:57:49 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA14201
          for hackers-outgoing; Wed, 2 Jul 1997 09:57:49 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA14193
          for <freebsd-hackers@freebsd.org>; Wed, 2 Jul 1997 09:57:45 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0wjSeN-00018c-00; Wed, 2 Jul 1997 09:53:03 -0700
Date: Wed, 2 Jul 1997 09:53:03 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: "Freeman P. Pascal IV" <pascal@compute.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: Problems with onboard Adaptec 7870 on Intel ALTServer motherboard...
In-Reply-To: <33BA757E.344C05E1@compute.com>
Message-ID: <Pine.BSF.3.95q.970702094727.4275B-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Wed, 2 Jul 1997, Freeman P. Pascal IV wrote:

> I have upgraded to 2.2.2-RELEASE as recommended, and that has

  You should now cvsup to 2.2-stable, which contains additional patches.

..
> lots of files removed.  There's no record of a cause.  I suspect
> that the system is panicing  while freeing an inode or something
> (this would explain lack of messages).

  Did you check "dmesg" for a cause?  If the disk is unwritable, kernel
messages are written into a RAM message buffer which is preserved accross
warm boots.

> I've swapped out the complete machine - only the disks are the
> same, and the problem persists.

  Somes drives just suck, and you will have problems with every os.  The
Grand Prix is notorious.  I hear this everywhere I go, whether Windows NT
or Netware.

> I wish I knew more about the scsi drivers, I'd put sometime into
> tracing the problem.  All I've been able to determine is that the
> error messages are coming from aic7xxx.c.
> 
> The errors I'm seeing are:
> 
> sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44
> SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3
> sd0(ahc0:0:0): abort message in message buffer
> sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54
> SEQADDR = 0x125 SCSISEQ = 0x12 SSTAT0 = 0x4 SSTAT1 = 0x3
> ahc0: Issued Channel A Bus Reset. 1 SCBs aborted
> Clearing bus reset
> Clearing 'in-reset' flag
> sd0(ahc0:0:0): no longer in timeout
> sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 
> , retries:3
> sd1(ahc0:1:0): UNIT ATTENTION asc:29,0
> sd1(ahc0:1:0):  Power on, reset, or bus device reset occurred
> , retries:2

  This is bad.  The drive is saying it was power cycled.  You should swap
this drive.
 
> sd2(ahc0:2:0): UNIT ATTENTION asc:29,0
> sd2(ahc0:2:0):  Power on, reset, or bus device reset occurred
> , retries:2
> 
> 
> It happens on all of the disks, mostly sd0 since it is the most
> accessed.
> 
> Any help would be appreciated - if I can't fix this, I'll have to
> switch to Solaris 2.5.1 X86 which I don't want to do.
> 
> -Freeman

Tom