From owner-freebsd-current@FreeBSD.ORG Sun Jun 28 09:14:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B7CC1065678 for ; Sun, 28 Jun 2009 09:14:12 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 204688FC08 for ; Sun, 28 Jun 2009 09:14:11 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 247011558; Sun, 28 Jun 2009 12:14:08 +0300 Message-ID: <4A47345B.3030209@FreeBSD.org> Date: Sun, 28 Jun 2009 12:14:03 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <4A4517BE.9040504@FreeBSD.org> <20090627164406.155f002d@ernst.jennejohn.org> <4A46553C.4000504@FreeBSD.org> <20090628110433.519c758a@ernst.jennejohn.org> In-Reply-To: <20090628110433.519c758a@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: RFC: ATA to CAM integration patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2009 09:14:12 -0000 Gary Jennejohn wrote: > Alexander Motin wrote: >> Gary Jennejohn wrote: >>> - remove atapicam from you kernel config file, otherwise the kernel >>> pancis in xpt (at least, mine did) >> Thank you for report. Problem is that atapicam provides fake emulated >> SPI transport, but not a native ATA in terms of updated CAM. Small >> attached patch fixes this for me: >> >> # camcontrol devlist >> at scbus0 target 0 lun 0 (pass0,ada0) >> at scbus3 target 0 lun 0 (cd0,pass1) >> > > Thanks a lot. This patch fixed the problem for me too. > > Any plans to update your original patch? Sure I will in few days. Just not after every single change. I am still investigating this issue to find real crash reason, that was triggered by this mistake. -- Alexander Motin