From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 31 17:15:56 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5A4866A for ; Wed, 31 Oct 2012 17:15:56 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 762318FC0A for ; Wed, 31 Oct 2012 17:15:56 +0000 (UTC) Received: from [10.198.122.141] (68.65.72.83.static-ip.telepacific.net [68.65.72.83]) (authenticated bits=0) by ns1.feral.com (8.14.5/8.14.4) with ESMTP id q9VHFnrd060005 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 31 Oct 2012 10:15:49 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <50915CC0.1090207@feral.com> Date: Wed, 31 Oct 2012 10:15:44 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: isp(4) broken in RELENG_9 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Wed, 31 Oct 2012 10:15:49 -0700 (PDT) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Matt Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 17:15:56 -0000 On 10/31/2012 8:25 AM, Joerg Pulz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi, > > somewhere on the road between RELENG_9_1 and RELENG_9 changes to > isp(4) make the driver unable to attach to the device. > > Here is the boot output of the failing RELENG_9: > > isp0: port 0x3000-0x30ff mem > 0xf7140000-0xf7143fff,0xf7200000-0xf72fffff irq 16 at device 0.0 on pci3 > isp0: error 22 loading dma map for control areas > isp0: Cannot setup DMA > device_attach: isp0 attach returned 6 > isp0: port 0x3400-0x34ff mem > 0xf7144000-0xf7147fff,0xf7300000-0xf73fffff irq 17 at device 0.1 on pci3 > isp0: error 22 loading dma map for control areas > isp0: Cannot setup DMA > device_attach: isp0 attach returned 6 Can we get a bit more info about the system you are running on? The only way this seems that it can happen is if more than one segment is created for the DMA maps of the queues, which, err, umm, would be wrong. The code is actually incorrect in an assumption it's making. It might have worked in previous releases, but the underlying mapping stuff may have changed and uncovered an issue.