From owner-aic7xxx Wed Apr 7 9:11: 5 1999 Delivered-To: aic7xxx@freebsd.org Received: from seahunt.imat.com (seahunt.imat.COM [140.174.70.10]) by hub.freebsd.org (Postfix) with ESMTP id F2A01157FB for ; Wed, 7 Apr 1999 09:11:01 -0700 (PDT) (envelope-from nelson@seahunt.imat.com) Received: (from nelson@localhost) by seahunt.imat.com (8.9.3/8.9.1a) id JAA07392; Wed, 7 Apr 1999 09:08:43 -0700 Date: Wed, 7 Apr 1999 09:08:43 -0700 From: Michael Nelson To: Doug Ledford Cc: Michael Nelson , linux-scsi@vger.rutgers.edu, aic7xxx@FreeBSD.ORG, linux-kernel@vger.rutgers.edu Subject: Re: aic7xxx driver update Message-ID: <19990407090843.A7365@seahunt.imat.com> Reply-To: nelson@imat.com References: <199904071528.IAA07140@seahunt.imat.com> <370B7E26.8C915D92@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <370B7E26.8C915D92@redhat.com>; from Doug Ledford on Wed, Apr 07, 1999 at 11:47:51AM -0400 Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 07, 1999 at 11:47:51AM -0400, Doug Ledford wrote: -> Which SCSI controller is giving the reset errors? The Ultra 2 Wide LVD one. -> Which device? The IBM DRVS09V ... 9.1 GB Ultra 2 Wide LVD -> What's the status of tagged queueing on your setup? Enabled, 16 commands. -> Does it identify the device before the problems start? Yes, it IDs the first controller, then the first scsi reset happens, then it IDs the second controller, more resets, then panic. -> What happens if you use the aic7xxx=no_reset flag on bootup? Haven't tried that. I was under the impression we were strongly discouraged from using it, but I'll try it and get back to you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message