From owner-freebsd-scsi@FreeBSD.ORG  Sat Apr  5 21:39:23 2003
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
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 5366037B401
	for <freebsd-scsi@freebsd.org>; Sat,  5 Apr 2003 21:39:23 -0800 (PST)
Received: from hub.org (hub.org [64.117.224.146])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D035D43FA3
	for <freebsd-scsi@freebsd.org>; Sat,  5 Apr 2003 21:39:22 -0800 (PST)
	(envelope-from scrappy@hub.org)
Received: from hub.org (hub.org [64.117.224.146])
	by hub.org (Postfix) with ESMTP
	id 74A5A1038EB0; Sun,  6 Apr 2003 01:39:20 -0400 (AST)
Date: Sun, 6 Apr 2003 01:39:20 -0400 (AST)
From: "Marc G. Fournier" <scrappy@hub.org>
To: Scott Long <scott_long@btc.adaptec.com>
In-Reply-To: <20030405121748.GA36962@hollin.btc.adaptec.com>
Message-ID: <20030406013806.A14933@hub.org>
References: <20030405005921.G613@atelier.acadiau.ca>
 <20030405121748.GA36962@hollin.btc.adaptec.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-scsi@freebsd.org
cc: "Marc G. Fournier" <marc.fournier@acadiau.ca>
Subject: Re: kernel errors in messages about enclosure ...
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 05:39:23 -0000

On Sat, 5 Apr 2003, Scott Long wrote:

> I don't speak SES very well, and it's hard to say if the returned data is
> getting magled by the RAID firmware.  An interesting test might be to enable
> the aacp and ses devices (and cam, of course) and see if the ses driver
> attaches to the hardware.

'K, how do you 'enable cam'?  Is that just the 'device pass' entry?

BTW, are there any plans to CAMify the aac driver?