From owner-freebsd-drivers@freebsd.org Thu Nov 7 20:06:54 2019 Return-Path: Delivered-To: freebsd-drivers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BA0E71BF5C6 for ; Thu, 7 Nov 2019 20:06:54 +0000 (UTC) (envelope-from cross@distal.com) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254:11::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 478DvK5mygz4G2F for ; Thu, 7 Nov 2019 20:06:53 +0000 (UTC) (envelope-from cross@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.15.2/8.15.2) with ESMTPSA id xA7K6jmo052862 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 7 Nov 2019 15:06:52 -0500 (EST) (envelope-from cross@distal.com) Received: from westeros.distal.com (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail.distal.com (8.15.2/8.15.2) with ESMTPS id xA7K6g5V022261 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Nov 2019 15:06:43 -0500 (EST) (envelope-from cross@westeros.distal.com) Received: (from cross@localhost) by westeros.distal.com (8.15.2/8.15.2/Submit) id xA7K6gNj022260; Thu, 7 Nov 2019 15:06:42 -0500 (EST) (envelope-from cross) Date: Thu, 7 Nov 2019 15:06:42 -0500 From: Chris Ross To: freebsd-drivers@freebsd.org Cc: cross+freebsd@distal.com Subject: Cisco 12G SAS RAID support in mpr(4) Message-ID: <20191107200642.GP1177@westeros.distal.com> References: <20191105183448.GE1177@westeros.distal.com> <65e90493-a038-5668-45e9-5101c52c23eb@quip.cz> <20191105201942.GF1177@westeros.distal.com> <20191105210409.GG1177@westeros.distal.com> <20191105220441.GH1177@westeros.distal.com> <20191106211248.GM1177@westeros.distal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191106211248.GM1177@westeros.distal.com> User-Agent: Mutt/1.10.0 (2018-05-17) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mail.distal.com [IPv6:::1]); Thu, 07 Nov 2019 15:06:43 -0500 (EST) X-Rspamd-Queue-Id: 478DvK5mygz4G2F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of cross@distal.com designates 2001:470:e254:11::4 as permitted sender) smtp.mailfrom=cross@distal.com X-Spamd-Result: default: False [-4.83 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-drivers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[distal.com]; IP_SCORE(-2.53)[ip: (-4.51), ipnet: 2001:470::/32(-4.62), asn: 6939(-3.49), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; TAGGED_FROM(0.00)[freebsd]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2019 20:06:54 -0000 Referencing a thread in freebsd-stable, I am trying to get FreeBSD 12.x booted and installed onto a Cisco UCS-C220M5 with a UCSC-RAID-M5 controller. https://docs.freebsd.org/cgi/getmsg.cgi?fetch=25822+0+current/freebsd-stable My controller looks to be based on a LSI 3516, but is not recognized by the mpr(4) driver. It's PCI vendor:device is 0x1000:0x0014. http://pci-ids.ucw.cz/read/PC/1000 shows it as a MegaRAID Tri-Mode SAS3516, but only the 0x00AA and 0x00AB are recognized as that by mpr(4) today. (device id 0x00AA doesn't show up in databases I find online, interestingly.) I added the device id into mpr(4), and the following errors happened. Can someone on this list advise me in where to look next, or towards someone familiar with the mpr(4) driver specifically? Thank you... - Chris On Wed, Nov 06, 2019 at 04:12:48PM -0500, Chris Ross wrote: > Okay. Well, the simple try didn't magically work. I added a few lines in > dev/mpr/mpr_pci.c in releng/12.0, built a new ISO, and booted. Now it > recognizes the part, but says the following: > > pcib7: [...] > pci7: numa-domain 0 on pcib7 > mpr0: port 0x7000-0x70ff mem 0xb8000000-0xb80fffff,0xb7f00000-0xb7ffffff,0xb7e00000-0xb7efffff at device 0.0 numa-domain 0 on pci7 > mpr0: IOC in fault state 0x0, resetting > mpr0: IOC in fault state 0x0, resetting > mpr0: IOC in fault state 0x0, resetting > mpr0: IOC in fault state 0x0, resetting > mpr0: IOC in fault state 0x0, resetting > mpr0: IOC in fault state 0x0, resetting > > There is about a 4 second pause between each of the "in fault state, resetting" > lines.