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>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.970311171919.14848A-100000>