From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 09:08:03 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CBD1106566C for ; Wed, 26 Jan 2011 09:08:03 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop2b.sarenet.es (proxypop2b.sarenet.es [194.30.0.107]) by mx1.freebsd.org (Postfix) with ESMTP id CA8358FC0C for ; Wed, 26 Jan 2011 09:08:02 +0000 (UTC) Received: from [172.16.1.55] (ssglan.sare.net [192.148.167.100]) by proxypop2b.sarenet.es (Postfix) with ESMTP id ECE8E732D3; Wed, 26 Jan 2011 10:08:00 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20110120170046.GA40879@nargothrond.kdm.org> Date: Wed, 26 Jan 2011 10:08:01 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110120170046.GA40879@nargothrond.kdm.org> To: Kenneth D. Merry X-Mailer: Apple Mail (2.1082) Cc: freebsd-scsi@freebsd.org Subject: Re: mps questions X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 09:08:03 -0000 On Jan 20, 2011, at 6:00 PM, Kenneth D. Merry wrote: >> And this happens no matter how I connect the internal SAS connectors. = There are two connectors from the disk backplanes to the card, SAS0 and = SAS1 (I assume they are two buses) and even if I reverse them I still = see eight disks.=20 >>=20 >=20 > I assume you mean you still see six disks... Yes, sorry :) Neuron short circuit. > If you see all the disks in the LSI BIOS, it most likely means there = is a > driver bug that is keeping FreeBSD from seeing all the disks. >=20 > Try booting with -v (boot -v at the boot loader prompt) and send the = full > dmesg output. That will cause the driver to print some additional > information when it probes. The dmesg is rather long, but maybe the list of mps related messages wil = be enough? (output follows at the end of the message) > After that, try booting with hw.mps.N.debug_level=3D1 set in = loader.conf, > where N is either 0 or 1, depending on which mps instance is having = the > problem. >=20 > You can turn it off via sysctl after you boot. Next thing to try :) boot -v yields the following messages. Curious thing, I don't see the = backplane as a device. Shouldn't it show up? I guess it would be that = "edge expander" Jan 26 09:30:26 kernel: mps0: port 0xfc00-0xfcff mem = 0xdf2b0000-0xdf2bffff,0xdf2c0000-0xdf2fffff irq 32 at device 0.0 on pci2 Jan 26 09:30:26 kernel: mps0: Reserved 0x10000 bytes for rid 0x14 type = 3 at 0xdf2b0000 Jan 26 09:30:26 kernel: mps0: Firmware: 02.15.63.00 Jan 26 09:30:26 kernel: mps0: IOCCapabilities: = 185c Jan 26 09:30:26 kernel: mps0: attempting to allocate 1 MSI-X vectors = (15 supported) Jan 26 09:30:26 kernel: mps0: using IRQ 258 for MSI-X Jan 26 09:30:26 kernel: mps0: [MPSAFE] Jan 26 09:30:26 kernel: mps0: [ITHREAD] Jan 26 09:30:26 kernel: mps0: Found device = <1902,Edge Expander> <6.0Gbps> <0x000a> <2/0> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000b> <2/0> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000c> <2/4> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000d> <2/5> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000e> <2/1> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000f> <2/2> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x0010> <2/3> Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: pass0 at mps0 bus 0 scbus0 target 1 lun 0 Jan 26 09:30:26 kernel: pass1 at mps0 bus 0 scbus0 target 2 lun 0 Jan 26 09:30:26 kernel: pass2 at mps0 bus 0 scbus0 target 3 lun 0 Jan 26 09:30:26 kernel: pass3 at mps0 bus 0 scbus0 target 4 lun 0 Jan 26 09:30:26 kernel: pass4 at mps0 bus 0 scbus0 target 5 lun 0 Jan 26 09:30:26 kernel: pass5 at mps0 bus 0 scbus0 target 6 lun 0 Jan 26 09:30:26 kernel: da0 at mps0 bus 0 scbus0 target 1 lun 0 Jan 26 09:30:26 kernel: da1 at mps0 bus 0 scbus0 target 2 lun 0 Jan 26 09:30:26 kernel: da2 at mps0 bus 0 scbus0 target 3 lun 0 Jan 26 09:30:26 kernel: da3 at mps0 bus 0 scbus0 target 4 lun 0 Jan 26 09:30:26 kernel: da4 at mps0 bus 0 scbus0 target 5 lun 0 Jan 26 09:30:26 kernel: da5 at mps0 bus 0 scbus0 target 6 lun 0 #=20