From owner-freebsd-current Wed Apr 28 13:18:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1453315796 for ; Wed, 28 Apr 1999 13:18:54 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA15382; Wed, 28 Apr 1999 21:50:01 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.6.12) id VAA01921; Wed, 28 Apr 1999 21:38:45 +0200 (CEST) From: Wilko Bulte Message-Id: <199904281938.VAA01921@yedi.iaf.nl> Subject: Re: Further on tape & CAM problems In-Reply-To: <199904281826.OAA37667@neunacht.netgsi.com> from "Christopher T. Johnson" at "Apr 28, 1999 2:26:24 pm" To: cjohnson@neunacht.netgsi.com (Christopher T. Johnson) Date: Wed, 28 Apr 1999 21:38:45 +0200 (CEST) Cc: dillon@apollo.backplane.com, shocking@prth.pgs.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Christopher T. Johnson wrote ... > REGARDLESS! > The drive is reporting an error condition and that error is NOT > getting back to user land. I've verified the problem with amdump Oh? Where/what is the error, does the console tell you? > amflush and dd. In ALL cases once the amber light goes on solid > systat -vmstat shows a solid 1.4MB/second data transfer into > never never land. That sounds like a bug. But it could be CAM not understanding that the 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte lockup.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message