From owner-freebsd-current Mon Apr 3 17:30:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA24728 for current-outgoing; Mon, 3 Apr 1995 17:30:56 -0700 Received: from estienne.cs.berkeley.edu (estienne.CS.Berkeley.EDU [128.32.42.147]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA24722 for ; Mon, 3 Apr 1995 17:30:54 -0700 Received: from localhost (localhost [127.0.0.1]) by estienne.cs.berkeley.edu (8.6.11/8.6.9) with SMTP id RAA08552; Mon, 3 Apr 1995 17:30:33 -0700 Message-Id: <199504040030.RAA08552@estienne.cs.berkeley.edu> X-Authentication-Warning: estienne.cs.berkeley.edu: Host localhost didn't use HELO protocol To: bob@obiwan.pmr.com (Bob Willcox) cc: freebsd-current@freefall.cdrom.com (freebsd-current) Subject: Re: aic7xxx.c: Target Busy console messages In-reply-to: Your message of "Mon, 03 Apr 1995 18:32:01 CDT." Date: Mon, 03 Apr 1995 17:30:32 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >I have noticed that with my new AHA-2740 controller card I get repetitive > >ahc0: Target Busy > >Messages on the console when accessing my Exabyte 8200 tape drive. Did the probe say that it was a tagged queuing device? Does the device actually work regardless of the messages? >Is this message important? (The bt742a.c driver appears to not >issue a message for a busy status.) From the Exabyte EXB-8200 >User's Manual: > > "Busy status indicates the EXB-8200 is in the busy state. The > EXB-8200 is in a busy state when it is performing an internal > operation that prevents it from accepting another command until > the operation is complete. > > The EXB-8200 returns Busy status for a command request until > the busy state is released. After the busy state is released, > the initiator must reissue the command to the EXB-8200. When > the busy state is released, selection operation and commands > can be executed normally." > >>From this, it sounds to me that this is a rather normal condition >and that the driver should simply reissue the command (periodically) >until successful. Is this true of other devices as well? It does reissue the command. It just doesn't happen that often so I log it to the console. > >Comments? > >-- >Bob Willcox >bob@obiwan.pmr.com (or obiwan%bob@uunet.uu.net) >Austin, TX -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================