From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 15 07:24:22 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26A5F16A4CE for ; Mon, 15 Mar 2004 07:24:22 -0800 (PST) Received: from eagle.plab.ku.dk (eagle.plab.ku.dk [130.225.107.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0D3C43D46 for ; Mon, 15 Mar 2004 07:24:21 -0800 (PST) (envelope-from tolid@plab.ku.dk) Received: from eagle.plab.ku.dk (localhost [127.0.0.1]) by eagle.plab.ku.dk (Postfix) with SMTP id 23B39E40C; Mon, 15 Mar 2004 16:24:20 +0100 (CET) Date: Mon, 15 Mar 2004 16:24:19 +0100 From: Anatoliy Dmytriyev To: freebsd-scsi@freebsd.org, scsi_fc_group@yahoo.com Message-Id: <20040315162419.52680188@eagle.plab.ku.dk> In-Reply-To: <20040310065354.83880.qmail@web13012.mail.yahoo.com> References: <20040310065354.83880.qmail@web13012.mail.yahoo.com> Organization: The Protein Laboratory, University of Copenhagen X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: BDR messages for Adaptec card X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 15:24:22 -0000 On Tue, 9 Mar 2004 22:53:54 -0800 (PST) fc scsi wrote: > Hi, > > I enabled CAMDEBUG in the kernel and got the logs at the time the problem > happens. I have trimmed down the logs considerably as it generated a huge > file. If after looking at the logs someone can even explain me what the > problem might be (without bothering for the solution) it would be a great > help. > > Thanks. > > fc scsi wrote: > > Hi, > > I am getting the error messages mentioned below on my system using the > following Adaptec card on FreeBSD 4.7: > > ======================================================================== > > ahc0: port 0xde00-0xdeff mem > 0xfe9df000-0 I had the same problem with . Somebody said that problem is in broken hard drives but in my case I found problem in the bad scsi terminator. So, try to check it and maybe it can help you. Best regards, Anatoliy Dmytriyev -- Anatoliy Dmytriyev