Date: Wed, 31 Oct 2012 10:15:44 -0700 From: Matthew Jacob <mj@feral.com> To: freebsd-scsi@freebsd.org Subject: Re: isp(4) broken in RELENG_9 Message-ID: <50915CC0.1090207@feral.com> In-Reply-To: <alpine.BSF.2.00.1210311616350.1938@unqrf.nqzva.sez2> References: <alpine.BSF.2.00.1210311616350.1938@unqrf.nqzva.sez2>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Qlogic ISP 2532 PCI FC-AL Adapter> 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: <Qlogic ISP 2532 PCI FC-AL Adapter> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50915CC0.1090207>