From owner-freebsd-hackers  Tue Mar 11 17:52:04 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA01143
          for hackers-outgoing; Tue, 11 Mar 1997 17:52:04 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA01101
          for <hackers@freebsd.org>; Tue, 11 Mar 1997 17:51:57 -0800 (PST)
Received: from misery.sdf.com [204.244.213.33] 
	by misery.sdf.com with smtp (Exim 1.59 #1)
	id 0w4dCY-0004FQ-00; Tue, 11 Mar 1997 17:51:34 -0800
Date: Tue, 11 Mar 1997 17:51:34 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: gibbs@freefall.freebsd.org, hackers@freebsd.org
Subject: Panic with ahc driver
Message-ID: <Pine.NEB.3.94.970311171919.14848A-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


  I'm getting:

panic: ahc1:A:0: Target did not send an IDENTIFY message.  LASTPHASE =
0x0, SAVED_TCL = 0x0


  on a 2.1.7 system.  Since it appears that 2.1.7 and 2.2 have the same
ahc driver, I guess it would happen there too.

  I'm using a Adaptec 3940UW and several Seagate Barracuda 4LP drives.

  I reliably reproduce this panic by running 4 parrallel "dd" processes
for 1 to 2 hours (write file, delete, write file, delete, etc).

  tagenable is on, but the panic occurs without or without tagged
commands.

  I've looked at the code, and there is a comment in NO_IDENT case about
alternatives to a panic.  Is it really that serious?  If I converted the
panic() call to a printf() could I really break something badly? :)


Tom