From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 01:29:00 2012 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 8A2C0106564A for ; Sun, 26 Feb 2012 01:29:00 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 376418FC08 for ; Sun, 26 Feb 2012 01:28:59 +0000 (UTC) Received: by qcsg15 with SMTP id g15so283477qcs.13 for ; Sat, 25 Feb 2012 17:28:59 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.229.102.72 as permitted sender) client-ip=10.229.102.72; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.229.102.72 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.229.102.72]) by 10.229.102.72 with SMTP id f8mr5109900qco.51.1330219739588 (num_hops = 1); Sat, 25 Feb 2012 17:28:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=YGc+38zBXDXIJBSmdBNCB4zwM6cNSrJcIrKGrr5sZ7A=; b=GtTVVRvUcTAQUUpf4IdWpOptmrtNSrZx1sQH4Car81BOgrCZEEUKffmTGfZRC3bfPU F7mxQCoUlu6qtkLgaG56d/MbBRRMPOw+e5lAFkeGdBMWV9jP+Ndzi88xFXB7bjwADptE iEIa8phV0hFgWV3r2GumHmGFFPrZL3yWno6eo= MIME-Version: 1.0 Received: by 10.229.102.72 with SMTP id f8mr4221545qco.51.1330219739490; Sat, 25 Feb 2012 17:28:59 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sat, 25 Feb 2012 17:28:59 -0800 (PST) In-Reply-To: <4F494676.2000909@fuckner.net> References: <4F494676.2000909@fuckner.net> Date: Sat, 25 Feb 2012 17:28:59 -0800 Message-ID: From: "bsalinux@gmail.com" To: Michael Fuckner Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-scsi@freebsd.org Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 01:29:00 -0000 Does this line look good? {0x1000, 0x0073, 0xffff, 0xffff, MFI_FLAGS_GEN2, "IBM ServeRAID M1015"}, /* M1015 */ Thanks On Sat, Feb 25, 2012 at 12:37 PM, Michael Fuckner wro= te: > Good evening, > > >> none3@pci0:1:0:0: =A0 =A0 =A0 class=3D0x010400 card=3D0x03b11014 chip=3D= 0x00731000 >> rev=3D0x03 hdr=3D0x00 >> =A0 =A0 vendor =A0 =A0 =3D 'LSI Logic / Symbios Logic' >> =A0 =A0 device =A0 =A0 =3D 'MegaRAID SAS 9240' >> =A0 =A0 class =A0 =A0 =A0=3D mass storage >> =A0 =A0 subclass =A0 =3D RAID > > > this looks like mfi (in Linux: megaraid_sas) should be responsible for > accessing this card. > Did you try to add device-ID into mfi_pci.c? > > Regards, > =A0Michael! > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" --=20 NOTICE: This email is a one to one communication and not for receiving any offers or a mass relay of emails. Please refrain from subscribing this email address to any of the mailing lists. All / any mass emails to this address will be considered as SPAM and will be reported to FTC and other authorities. Thanks. From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 02:04:59 2012 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 1B8A7106564A for ; Sun, 26 Feb 2012 02:04:59 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id BE3648FC0A for ; Sun, 26 Feb 2012 02:04:58 +0000 (UTC) Received: by qao25 with SMTP id 25so886873qao.13 for ; Sat, 25 Feb 2012 18:04:57 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.229.137.80 as permitted sender) client-ip=10.229.137.80; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.229.137.80 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.229.137.80]) by 10.229.137.80 with SMTP id v16mr5197787qct.31.1330221897936 (num_hops = 1); Sat, 25 Feb 2012 18:04:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=P9jLZmAZ6IlrU0PsbDpBB4geLfd9mGHJMqhP9jjAZJU=; b=psYGbx+32SytaAt7eWNiprDnSc17mvx15UIpjwpthw+6buwZG4S29lFv6k/ovLizNX CCd/6/kHYkM0/kZWblgqnRMrc+uNTrjLILNsFOAnrXj78zlDhPfg9pjoBhbx4hiF1nGR fRhQsjbEHs59VQivF0q7IR0QCeY+81zYp1b7E= MIME-Version: 1.0 Received: by 10.229.137.80 with SMTP id v16mr4277996qct.31.1330221897815; Sat, 25 Feb 2012 18:04:57 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sat, 25 Feb 2012 18:04:57 -0800 (PST) In-Reply-To: References: <4F494676.2000909@fuckner.net> Date: Sat, 25 Feb 2012 18:04:57 -0800 Message-ID: From: "bsalinux@gmail.com" To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 02:04:59 -0000 I installed a new kernel with thmodified mfi_pci.c. Dmesg reports the devic= e mfi0: port 0xe000-0xe0ff mem 0xfe460000-0xfe463fff,0xfe400000-0xfe43ffff irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 3.00 mfi0: Frame 0xffffff80002b0000 timed out command 0xCB6B4040 mfi0: failed to send init command device_attach: mfi0 attach returned 60 but it fails to init. Thanks. On Sat, Feb 25, 2012 at 5:28 PM, bsalinux@gmail.com wr= ote: > Does this line look good? > > =A0{0x1000, 0x0073, 0xffff, 0xffff, MFI_FLAGS_GEN2, "IBM ServeRAID > M1015"}, /* M1015 =A0*/ > > Thanks > > On Sat, Feb 25, 2012 at 12:37 PM, Michael Fuckner w= rote: >> Good evening, >> >> >>> none3@pci0:1:0:0: =A0 =A0 =A0 class=3D0x010400 card=3D0x03b11014 chip= =3D0x00731000 >>> rev=3D0x03 hdr=3D0x00 >>> =A0 =A0 vendor =A0 =A0 =3D 'LSI Logic / Symbios Logic' >>> =A0 =A0 device =A0 =A0 =3D 'MegaRAID SAS 9240' >>> =A0 =A0 class =A0 =A0 =A0=3D mass storage >>> =A0 =A0 subclass =A0 =3D RAID >> >> >> this looks like mfi (in Linux: megaraid_sas) should be responsible for >> accessing this card. >> Did you try to add device-ID into mfi_pci.c? >> >> Regards, >> =A0Michael! >> >> >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > -- > NOTICE: This email is a one to one communication and not for receiving > any offers or a mass relay of emails. Please refrain from subscribing > this email address to any of the mailing lists. All / any mass emails > to this address will be considered as SPAM and will be reported to FTC > and other authorities. Thanks. --=20 NOTICE: This email is a one to one communication and not for receiving any offers or a mass relay of emails. Please refrain from subscribing this email address to any of the mailing lists. All / any mass emails to this address will be considered as SPAM and will be reported to FTC and other authorities. Thanks. From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 06:24:37 2012 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 18F0D106566B for ; Sun, 26 Feb 2012 06:24:36 +0000 (UTC) (envelope-from michael@fuckner.net) Received: from dedihh.fuckner.net (dedihh.fuckner.net [81.209.183.161]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1208FC08 for ; Sun, 26 Feb 2012 06:24:36 +0000 (UTC) Received: from dedihh.fuckner.net (localhost [127.0.0.1]) by dedihh.fuckner.net (Postfix) with ESMTP id 121C4110A4 for ; Sun, 26 Feb 2012 07:24:35 +0100 (CET) X-Virus-Scanned: amavisd-new at fuckner.net Received: from dedihh.fuckner.net ([127.0.0.1]) by dedihh.fuckner.net (dedihh.fuckner.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id MjeGC-x3vChE for ; Sun, 26 Feb 2012 07:24:29 +0100 (CET) Received: from c64.rebootking.de (e176141102.adsl.alicedsl.de [85.176.141.102]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by dedihh.fuckner.net (Postfix) with ESMTPSA id 288511109C for ; Sun, 26 Feb 2012 07:24:29 +0100 (CET) Message-ID: <4F49D01C.4020304@fuckner.net> Date: Sun, 26 Feb 2012 07:24:28 +0100 From: Michael Fuckner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4F494676.2000909@fuckner.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 06:24:37 -0000 On 02/26/2012 03:04 AM, bsalinux@gmail.com wrote: > I installed a new kernel with thmodified mfi_pci.c. Dmesg reports the device > > mfi0: port 0xe000-0xe0ff mem > 0xfe460000-0xfe463fff,0xfe400000-0xfe43ffff irq 16 at device 0.0 on > pci1 > mfi0: Megaraid SAS driver Ver 3.00 > mfi0: Frame 0xffffff80002b0000 timed out command 0xCB6B4040 > mfi0: failed to send init command > device_attach: mfi0 attach returned 60 > > but it fails to init. that's what I thought- the 9240 is not a real megaraid, not an HBA. Just an 2008-HBA-Chip bases Card on steroids pretending to be a megaraid- without Caches/ BBU... Michael! From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 06:34:51 2012 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 78A2E1065672 for ; Sun, 26 Feb 2012 06:34:51 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD718FC18 for ; Sun, 26 Feb 2012 06:34:50 +0000 (UTC) Received: by qadz30 with SMTP id z30so724751qad.13 for ; Sat, 25 Feb 2012 22:34:50 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.224.111.142 as permitted sender) client-ip=10.224.111.142; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.224.111.142 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.224.111.142]) by 10.224.111.142 with SMTP id s14mr5508479qap.78.1330238090349 (num_hops = 1); Sat, 25 Feb 2012 22:34:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=KPQFcFz4dTJITRhGMebLu3ZxcILzte1vTxDU5lHA2R0=; b=omHT2bUV4FdwPZaEubAkby0cDWV1ht2Roqb2aw+IltlZIlbAsjwrp1eZFbCvINXpx8 sllG/JZKtyKzKb2GPL22YaIkHVsZoZj4g8QbQh6f1AOYdE+qlVM7G1FHv2pg4P8Gd/B/ GZZR1TfOSnCnUDtumgK65mvJtxnlq4ROZwD1g= MIME-Version: 1.0 Received: by 10.224.111.142 with SMTP id s14mr4664494qap.78.1330238090289; Sat, 25 Feb 2012 22:34:50 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sat, 25 Feb 2012 22:34:50 -0800 (PST) In-Reply-To: <4F49D01C.4020304@fuckner.net> References: <4F494676.2000909@fuckner.net> <4F49D01C.4020304@fuckner.net> Date: Sat, 25 Feb 2012 22:34:50 -0800 Message-ID: From: "bsalinux@gmail.com" To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 06:34:51 -0000 Just need HBA functionality at this moment. On Sat, Feb 25, 2012 at 10:24 PM, Michael Fuckner wrote: > that's what I thought- the 9240 is not a real megaraid, not an HBA. Just an > 2008-HBA-Chip bases Card on steroids pretending to be a megaraid- without From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 07:51:29 2012 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 AFA49106566B for ; Sun, 26 Feb 2012 07:51:29 +0000 (UTC) (envelope-from michael@fuckner.net) Received: from dedihh.fuckner.net (dedihh.fuckner.net [81.209.183.161]) by mx1.freebsd.org (Postfix) with ESMTP id 65CDB8FC13 for ; Sun, 26 Feb 2012 07:51:29 +0000 (UTC) Received: from dedihh.fuckner.net (localhost [127.0.0.1]) by dedihh.fuckner.net (Postfix) with ESMTP id 6CDBB11369 for ; Sun, 26 Feb 2012 08:51:28 +0100 (CET) X-Virus-Scanned: amavisd-new at fuckner.net Received: from dedihh.fuckner.net ([127.0.0.1]) by dedihh.fuckner.net (dedihh.fuckner.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id DYgNjZ9EpwNj for ; Sun, 26 Feb 2012 08:51:22 +0100 (CET) Received: from c64.rebootking.de (e176141102.adsl.alicedsl.de [85.176.141.102]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by dedihh.fuckner.net (Postfix) with ESMTPSA id C43891135A for ; Sun, 26 Feb 2012 08:51:22 +0100 (CET) Message-ID: <4F49E47A.5040105@fuckner.net> Date: Sun, 26 Feb 2012 08:51:22 +0100 From: Michael Fuckner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4F494676.2000909@fuckner.net> <4F49D01C.4020304@fuckner.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 07:51:29 -0000 On 02/26/2012 07:34 AM, bsalinux@gmail.com wrote: > Just need HBA functionality at this moment. I don't know if it is possible to flash the HBA-FW into this card- you'll probably brick it. From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 08:13:32 2012 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 CED011065670 for ; Sun, 26 Feb 2012 08:13:32 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 6E32A8FC0C for ; Sun, 26 Feb 2012 08:13:32 +0000 (UTC) Received: by qadz30 with SMTP id z30so739904qad.13 for ; Sun, 26 Feb 2012 00:13:31 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.229.77.141 as permitted sender) client-ip=10.229.77.141; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.229.77.141 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.229.77.141]) by 10.229.77.141 with SMTP id g13mr5527688qck.11.1330244011832 (num_hops = 1); Sun, 26 Feb 2012 00:13:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2J7ilJ2Lvq6XXw768FZIv/LXFXy4l8q6DVSGv/7VC+E=; b=r5P6FlA8sqTAh+x8C/aE0fK2UDOfqrtQv6IaCS+69vqCx0jbvrX25kTpparfF4WGhe bSXFigc1hG5Q+qeZxrGdPYG2TQbJERDAQtmyYwvHCPGB5JOtIqgNvRMlxUmZ2O6H3p4c ETZ3mnLO2q00uHQ9xgv8eBpoO+fI9vchX2H6E= MIME-Version: 1.0 Received: by 10.229.77.141 with SMTP id g13mr4539403qck.11.1330244011784; Sun, 26 Feb 2012 00:13:31 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sun, 26 Feb 2012 00:13:31 -0800 (PST) In-Reply-To: <4F49E47A.5040105@fuckner.net> References: <4F494676.2000909@fuckner.net> <4F49D01C.4020304@fuckner.net> <4F49E47A.5040105@fuckner.net> Date: Sun, 26 Feb 2012 00:13:31 -0800 Message-ID: From: "bsalinux@gmail.com" To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 08:13:32 -0000 Form the other threads it looks like people have flashed it to LSI 9240 IT firmware but results are mixed. Works for him (the firmware download url doesn't work) http://forums.freebsd.org/showpost.php?s=cdff845b508a26e4a7e3dbcca6ac2974&p=144921&postcount=8 http://forums.freebsd.org/showpost.php?s=cdff845b508a26e4a7e3dbcca6ac2974&p=136223&postcount=6 http://hardforum.com/showpost.php?p=1037333726&postcount=8 I could try flashing it but scared to brick the card. > > I don't know if it is possible to flash the HBA-FW into this card- you'll > probably brick it. From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 08:16:58 2012 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 EC470106566B for ; Sun, 26 Feb 2012 08:16:57 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9E4608FC08 for ; Sun, 26 Feb 2012 08:16:57 +0000 (UTC) Received: by qadz30 with SMTP id z30so740453qad.13 for ; Sun, 26 Feb 2012 00:16:57 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.229.136.196 as permitted sender) client-ip=10.229.136.196; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.229.136.196 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.229.136.196]) by 10.229.136.196 with SMTP id s4mr5449694qct.71.1330244217160 (num_hops = 1); Sun, 26 Feb 2012 00:16:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=SVJ68hmHFHey83kUOWbIbCAMpo62Sfclvj5jFOqYIRE=; b=KGEd3tU3U8GrUHwRIATHD7TGLA/BRxj6L1ilEaycDnR4LrkGi4tVdb1n+ZHX0CGs2R hxoVkLU857Nob79UGsft71XNGRHUmbi9dSic3MFrgIYmE16mdbOsuN+IKBmWZaQSlQZG f9BdDgtG5LFyJHkgWYD3j3QYMt3emdKrRjDGk= MIME-Version: 1.0 Received: by 10.229.136.196 with SMTP id s4mr4480104qct.71.1330244217108; Sun, 26 Feb 2012 00:16:57 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sun, 26 Feb 2012 00:16:56 -0800 (PST) In-Reply-To: <4F49E977.6040609@fuckner.net> References: <4F494676.2000909@fuckner.net> <4F49D01C.4020304@fuckner.net> <4F49E977.6040609@fuckner.net> Date: Sun, 26 Feb 2012 00:16:56 -0800 Message-ID: From: "bsalinux@gmail.com" To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 08:16:58 -0000 Thanks Michael, How confident are you that if the card is flashed to 9240 will work? Don't worry I won't blame you :-) Thanks. > > http://www.lsi.com/products/storagecomponents/Pages/MegaRAIDSAS9240-8i.as= px > > http://www.lsi.com/products/storagecomponents/Pages/LSISAS9210-8i.aspx > > You can try to flash LSI 9210-8i-fw under DOS environment- but I'm not su= re > if this works. I flashed IBM M1000 (I'm not exactly sure what IBM part it > was) to LSI 9210-4i4e. This worked, but those are both mpt2sas, not > megaraid_sas -> mpt2sas. > > IIRC I used the following commands > sas2flsh -o -e 6 -c 0 > sas2flsh -f 2118ir.bin -b mptsas2.rom -c 0 > > - you have to adjust the firmware file > - I just saw some options in sas2flsh -o -h: > > =A0 =A0 =A0 =A0-e x: =A0 =A0Erase selected controller's flash region > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x =3D Segment(s) of flash to erase > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 . . . Erase NVSRAM > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2 . . . Erase Backup Firmware > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3 . . . Erase Persistent Pages including = Manufacturing Pages > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4 . . . Manufacturing Parameter Block > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 5 . . . Boot Services > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 6 . . . Clean Flash (erase all except Man= ufacturing > Parameter Block) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 7 . . . Erase Complete Flash > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 8 . . . Erase MegaRAID Firmware > > > So perhaps -o -e 8 is what you want > > > But please don't blame me if you brick it, I rarely have IBM-HW in my han= ds > and I don't know if they are really exactly the same as the LSI cards. > > Regards, > =A0Michael! From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 08:35:23 2012 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 A6D86106564A for ; Sun, 26 Feb 2012 08:35:23 +0000 (UTC) (envelope-from martin@mullet.se) Received: from smtp.mullet.se (smtp.mullet.se [94.247.168.122]) by mx1.freebsd.org (Postfix) with ESMTP id 2EEB18FC08 for ; Sun, 26 Feb 2012 08:35:23 +0000 (UTC) Received: from mbp.gneto.com (ua-83-227-181-30.cust.bredbandsbolaget.se [83.227.181.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mullet.se (Postfix) with ESMTPSA id 6E2486270010 for ; Sun, 26 Feb 2012 09:16:23 +0100 (CET) Message-ID: <4F49EA56.2010101@mullet.se> Date: Sun, 26 Feb 2012 09:16:22 +0100 From: Martin Nilsson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4F494676.2000909@fuckner.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 08:35:23 -0000 It is probably supported by LSI:s mfi driver that is available on their web. It is horrible (32/64 bit unclean) and hard to install but it supports the skinny cards (9240) as well as the thunderbolt 9265/9285. Are there any effort going on to bring support for these cards into the stock mfi driver? On 2012-02-26 03:04, bsalinux@gmail.com wrote: > I installed a new kernel with thmodified mfi_pci.c. Dmesg reports the device > > mfi0: port 0xe000-0xe0ff mem > 0xfe460000-0xfe463fff,0xfe400000-0xfe43ffff irq 16 at device 0.0 on > pci1 > mfi0: Megaraid SAS driver Ver 3.00 > mfi0: Frame 0xffffff80002b0000 timed out command 0xCB6B4040 > mfi0: failed to send init command > device_attach: mfi0 attach returned 60 > > but it fails to init. > > Thanks. > > On Sat, Feb 25, 2012 at 5:28 PM, bsalinux@gmail.com wrote: >> Does this line look good? >> >> {0x1000, 0x0073, 0xffff, 0xffff, MFI_FLAGS_GEN2, "IBM ServeRAID >> M1015"}, /* M1015 */ >> >> Thanks >> >> On Sat, Feb 25, 2012 at 12:37 PM, Michael Fuckner wrote: >>> Good evening, >>> >>> >>>> none3@pci0:1:0:0: class=0x010400 card=0x03b11014 chip=0x00731000 >>>> rev=0x03 hdr=0x00 >>>> vendor = 'LSI Logic / Symbios Logic' >>>> device = 'MegaRAID SAS 9240' >>>> class = mass storage >>>> subclass = RAID >>> >>> this looks like mfi (in Linux: megaraid_sas) should be responsible for >>> accessing this card. >>> Did you try to add device-ID into mfi_pci.c? >>> >>> Regards, >>> Michael! >>> >>> >>> _______________________________________________ >>> freebsd-scsi@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >>> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" >> >> >> -- >> NOTICE: This email is a one to one communication and not for receiving >> any offers or a mass relay of emails. Please refrain from subscribing >> this email address to any of the mailing lists. All / any mass emails >> to this address will be considered as SPAM and will be reported to FTC >> and other authorities. Thanks. > > -- Martin Nilsson, CEO, Mullet Scandinavia AB, Malmö, SWEDEN E-mail: martin@mullet.se, Phone: +46-(0)708-59 99 91, Web: www.mullet.se Our business is well engineered servers optimised for FreeBSD& Linux From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 15:46:59 2012 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 D3BF6106564A for ; Sun, 26 Feb 2012 15:46:59 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f47.google.com (mail-qw0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 8A5608FC12 for ; Sun, 26 Feb 2012 15:46:59 +0000 (UTC) Received: by qadz30 with SMTP id z30so842873qad.13 for ; Sun, 26 Feb 2012 07:46:58 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.224.194.65 as permitted sender) client-ip=10.224.194.65; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.224.194.65 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.224.194.65]) by 10.224.194.65 with SMTP id dx1mr7272374qab.90.1330271218955 (num_hops = 1); Sun, 26 Feb 2012 07:46:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U1ENSUKfu1IXljiOWYmn8sk2XNpW/SSrSDwg37SsMxc=; b=afARX8lA8QVksshbeAf8mM7TOrdjQGFe4RpsRNo15h/0XxUu+Nuom/uzRWfPvKrPte 16wpY3CVlr8XQtGpKtsIqpCALNx9AlwNS89Zn6VnlbcmUgWkZ9Cjl4/3srgUJ5YWaut4 pT5YHW+pvW5gzDdiy72dS2ooPHqucSFBo9gdg= MIME-Version: 1.0 Received: by 10.224.194.65 with SMTP id dx1mr6145864qab.90.1330271218920; Sun, 26 Feb 2012 07:46:58 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sun, 26 Feb 2012 07:46:58 -0800 (PST) In-Reply-To: <4F49EA56.2010101@mullet.se> References: <4F494676.2000909@fuckner.net> <4F49EA56.2010101@mullet.se> Date: Sun, 26 Feb 2012 07:46:58 -0800 Message-ID: From: "bsalinux@gmail.com" To: Martin Nilsson Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-scsi@freebsd.org Subject: Re: IBM M1015 support 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: Sun, 26 Feb 2012 15:46:59 -0000 Another positive link that I found http://forums.freenas.org/showthread.php?3577-Is-my-Hardware-Compatable&p=15519&viewfull=1#post15519 I'll try that later today. From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 26 21:17:56 2012 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 59543106566C for ; Sun, 26 Feb 2012 21:17:56 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.c2i.net [212.247.154.130]) by mx1.freebsd.org (Postfix) with ESMTP id DB4268FC14 for ; Sun, 26 Feb 2012 21:17:55 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 241858659 for freebsd-scsi@freebsd.org; Sun, 26 Feb 2012 22:07:52 +0100 From: Hans Petter Selasky To: freebsd-scsi@freebsd.org Date: Sun, 26 Feb 2012 22:06:08 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201202262206.08378.hselasky@c2i.net> Subject: CAM layer gets stuck when sim->refcount > 0 at UMASS detach (10-current) 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: Sun, 26 Feb 2012 21:17:56 -0000 Hi, When running a stress test on a USB mass storage device, the CAM layer will eventually block at detach, because the refcount is not going towards zero on the SIM structure. Test script: ugenX.Y is a mass storage device #!/bin/sh while true do usbconfig -d ugenX.Y reset echo "." done After a minute or two the printouts above stops because the CAM layer is not releasing the reference count, indicating a bug somewhere during probe of the newly attached device. Any patches, ideas or things you want me to test? Please CC me hence I'm not subscribed to this list. --HPS From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 02:57:22 2012 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 3BA2A106566C for ; Mon, 27 Feb 2012 02:57:22 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog120.obsmtp.com (na3sys009aog120.obsmtp.com [74.125.149.140]) by mx1.freebsd.org (Postfix) with ESMTP id A4BDA8FC08 for ; Mon, 27 Feb 2012 02:57:21 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob120.postini.com ([74.125.148.12]) with SMTP ID DSNKT0rxEJXvSQaF2r4wwo3dbjOPfzo0OcNm@postini.com; Sun, 26 Feb 2012 18:57:21 PST Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 26 Feb 2012 22:01:58 -0500 Received: from inbexch01.lsi.com (135.36.98.37) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 26 Feb 2012 21:57:19 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch01.lsi.com ([135.36.98.37]) with mapi; Mon, 27 Feb 2012 08:27:16 +0530 From: "Desai, Kashyap" To: Martin Nilsson , "freebsd-scsi@freebsd.org" Date: Mon, 27 Feb 2012 08:27:11 +0530 Thread-Topic: IBM M1015 support Thread-Index: Acz0YZ1b8mBdFf7tRMyspURAj6lRKwAmYSiA Message-ID: References: <4F494676.2000909@fuckner.net> <4F49EA56.2010101@mullet.se> In-Reply-To: <4F49EA56.2010101@mullet.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: IBM M1015 support 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: Mon, 27 Feb 2012 02:57:22 -0000 > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of Martin Nilsson > Sent: Sunday, February 26, 2012 1:46 PM > To: freebsd-scsi@freebsd.org > Subject: Re: IBM M1015 support >=20 > It is probably supported by LSI:s mfi driver that is available on their > web. > It is horrible (32/64 bit unclean) and hard to install but it supports > the skinny cards (9240) as well as the thunderbolt 9265/9285. >=20 > Are there any effort going on to bring support for these cards into the > stock mfi driver? YES, LSI has plan to do mfi drivers changes in order to fix basic need for = customers. I am not sure which freebsd version will be the first one to get those chan= ges in. As of now I have this much information to share so wait for some more time = to get more info. ~ Kashyap >=20 > On 2012-02-26 03:04, bsalinux@gmail.com wrote: > > I installed a new kernel with thmodified mfi_pci.c. Dmesg reports the > device > > > > mfi0: port 0xe000-0xe0ff mem > > 0xfe460000-0xfe463fff,0xfe400000-0xfe43ffff irq 16 at device 0.0 on > > pci1 > > mfi0: Megaraid SAS driver Ver 3.00 > > mfi0: Frame 0xffffff80002b0000 timed out command 0xCB6B4040 > > mfi0: failed to send init command > > device_attach: mfi0 attach returned 60 > > > > but it fails to init. > > > > Thanks. > > > > On Sat, Feb 25, 2012 at 5:28 PM, > bsalinux@gmail.com wrote: > >> Does this line look good? > >> > >> {0x1000, 0x0073, 0xffff, 0xffff, MFI_FLAGS_GEN2, "IBM ServeRAID > >> M1015"}, /* M1015 */ > >> > >> Thanks > >> > >> On Sat, Feb 25, 2012 at 12:37 PM, Michael > Fuckner wrote: > >>> Good evening, > >>> > >>> > >>>> none3@pci0:1:0:0: class=3D0x010400 card=3D0x03b11014 > chip=3D0x00731000 > >>>> rev=3D0x03 hdr=3D0x00 > >>>> vendor =3D 'LSI Logic / Symbios Logic' > >>>> device =3D 'MegaRAID SAS 9240' > >>>> class =3D mass storage > >>>> subclass =3D RAID > >>> > >>> this looks like mfi (in Linux: megaraid_sas) should be responsible > for > >>> accessing this card. > >>> Did you try to add device-ID into mfi_pci.c? > >>> > >>> Regards, > >>> Michael! > >>> > >>> > >>> _______________________________________________ > >>> freebsd-scsi@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > >>> To unsubscribe, send any mail to "freebsd-scsi- > unsubscribe@freebsd.org" > >> > >> > >> -- > >> NOTICE: This email is a one to one communication and not for > receiving > >> any offers or a mass relay of emails. Please refrain from subscribing > >> this email address to any of the mailing lists. All / any mass emails > >> to this address will be considered as SPAM and will be reported to > FTC > >> and other authorities. Thanks. > > > > >=20 >=20 > -- > Martin Nilsson, CEO, Mullet Scandinavia AB, Malm=F6, SWEDEN > E-mail: martin@mullet.se, Phone: +46-(0)708-59 99 91, Web: www.mullet.se >=20 > Our business is well engineered servers optimised for FreeBSD& Linux >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 04:59:20 2012 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 DB9EA106564A for ; Mon, 27 Feb 2012 04:59:20 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0188FC18 for ; Mon, 27 Feb 2012 04:59:20 +0000 (UTC) Received: by qcsg15 with SMTP id g15so707163qcs.13 for ; Sun, 26 Feb 2012 20:59:20 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.224.86.137 as permitted sender) client-ip=10.224.86.137; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.224.86.137 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.224.86.137]) by 10.224.86.137 with SMTP id s9mr9869580qal.64.1330318760099 (num_hops = 1); Sun, 26 Feb 2012 20:59:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=npNJBde8ycD91KdjtZjtiOXVaarxig8sYKL3vq0oXSc=; b=j+L04FeWsCO2kvN3/My8TvPecQTQei2KEYy75hxVMHRA3dsfURZw287gsVvcSbplSm 7dkwXmvPhVPayepi7EpydaSs6+0g8Q+AQrBEJYnKl2t4fHUME2EPp8A0OLInv0GivbKy On5ILmV1QacgcDvjVfLM+JfsPNiNmoHYz9jQs= MIME-Version: 1.0 Received: by 10.224.86.137 with SMTP id s9mr8359753qal.64.1330318760064; Sun, 26 Feb 2012 20:59:20 -0800 (PST) Received: by 10.229.13.149 with HTTP; Sun, 26 Feb 2012 20:59:19 -0800 (PST) In-Reply-To: References: <4F494676.2000909@fuckner.net> <4F49EA56.2010101@mullet.se> Date: Sun, 26 Feb 2012 20:59:19 -0800 Message-ID: From: "bsalinux@gmail.com" To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: IBM M1015 support 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: Mon, 27 Feb 2012 04:59:20 -0000 Is there any current (development / beta driver) available? Thanks > YES, LSI has plan to do mfi drivers changes in order to fix basic need for customers. > > I am not sure which freebsd version will be the first one to get those changes in. > As of now I have this much information to share so wait for some more time to get more info. > > ~ Kashyap From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 11:07:46 2012 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 EF3471065672 for ; Mon, 27 Feb 2012 11:07:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD48A8FC19 for ; Mon, 27 Feb 2012 11:07:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1RB7jR7090337 for ; Mon, 27 Feb 2012 11:07:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1RB7jC3090334 for freebsd-scsi@FreeBSD.org; Mon, 27 Feb 2012 11:07:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Feb 2012 11:07:45 GMT Message-Id: <201202271107.q1RB7jC3090334@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org 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: Mon, 27 Feb 2012 11:07:46 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c f kern/163130 scsi [mpt] cannot dumpon to mpt connected disk o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153514 scsi [cam] [panic] CAM related panic o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c s kern/149927 scsi [cam] hard drive not stopped before removing power dur o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 49 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 15:30:52 2012 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE79F106567C; Mon, 27 Feb 2012 15:30:52 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A58388FC2A; Mon, 27 Feb 2012 15:30:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1RFUq5N042173; Mon, 27 Feb 2012 15:30:52 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1RFUqgj042141; Mon, 27 Feb 2012 15:30:52 GMT (envelope-from jh) Date: Mon, 27 Feb 2012 15:30:52 GMT Message-Id: <201202271530.q1RFUqgj042141@freefall.freebsd.org> To: danno@internet2.edu, jh@FreeBSD.org, freebsd-scsi@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/163130: [mpt] cannot dumpon to mpt connected disk 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: Mon, 27 Feb 2012 15:30:52 -0000 Synopsis: [mpt] cannot dumpon to mpt connected disk State-Changed-From-To: feedback->closed State-Changed-By: jh State-Changed-When: Mon Feb 27 15:30:51 UTC 2012 State-Changed-Why: Feedback timeout. http://www.freebsd.org/cgi/query-pr.cgi?pr=163130 From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 16:50:08 2012 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26DE2106564A for ; Mon, 27 Feb 2012 16:50:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 167BF8FC16 for ; Mon, 27 Feb 2012 16:50:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1RGo7jd014462 for ; Mon, 27 Feb 2012 16:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1RGo77i014461; Mon, 27 Feb 2012 16:50:07 GMT (envelope-from gnats) Date: Mon, 27 Feb 2012 16:50:07 GMT Message-Id: <201202271650.q1RGo77i014461@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Dan Pritts Cc: Subject: Re: kern/163130: [mpt] cannot dumpon to mpt connected disk X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Pritts List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 16:50:08 -0000 The following reply was made to PR kern/163130; it has been noted by GNATS. From: Dan Pritts To: bug-followup@FreeBSD.org, danno@internet2.edu Cc: Subject: Re: kern/163130: [mpt] cannot dumpon to mpt connected disk Date: Mon, 27 Feb 2012 11:28:52 -0500 Hi, I remember responding to this but I must have not hit "send" or something Your diagnosis was correct, we had the wrong partition type set. However, this requirement is not listed in the dumpon man page. It is implied in the "implementation notes"; "use one of the system swap devices". But I had successfully configured the partition in question as a swap device, so it seemed like I'd satisfied that requirement. It makes good sense to enforce this restriction. It'da be great to also have it spelled out explicitly in the man page. thanks danno -- Dan Pritts, Sr. Systems Engineer Internet2 office: +1-734-352-4953 | mobile: +1-734-834-7224 From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 17:47:16 2012 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 000EE1065676; Mon, 27 Feb 2012 17:47:15 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog125.obsmtp.com (na3sys009aog125.obsmtp.com [74.125.149.153]) by mx1.freebsd.org (Postfix) with ESMTP id 0A1978FC22; Mon, 27 Feb 2012 17:47:14 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob125.postini.com ([74.125.148.12]) with SMTP ID DSNKT0vBogM8vjOnFIKfu5dDdXBhRqFruvrn@postini.com; Mon, 27 Feb 2012 09:47:15 PST Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 27 Feb 2012 12:51:50 -0500 Received: from inbexch02.lsi.com (135.36.98.40) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 27 Feb 2012 12:47:13 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Mon, 27 Feb 2012 23:17:09 +0530 From: "Desai, Kashyap" To: John Baldwin , "freebsd-stable@freebsd.org" Date: Mon, 27 Feb 2012 23:17:07 +0530 Thread-Topic: mpslsi0 : Trying sleep, but thread marked as sleeping prohibited Thread-Index: AczzHWYQfkAel5RkSQGjugGiKVUEJQCWlyqQ Message-ID: References: <20120223092457.GB55074@deviant.kiev.zoral.com.ua> <201202230958.05667.jhb@freebsd.org> In-Reply-To: <201202230958.05667.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" , "Justin T. Gibbs" , "Kenneth D. Merry" , "McConnell, Stephen" Subject: RE: mpslsi0 : Trying sleep, but thread marked as sleeping prohibited 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: Mon, 27 Feb 2012 17:47:16 -0000 > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Thursday, February 23, 2012 8:28 PM > To: freebsd-stable@freebsd.org > Cc: Desai, Kashyap; Konstantin Belousov; freebsd-scsi@freebsd.org; > Kenneth D. Merry; Justin T. Gibbs; McConnell, Stephen > Subject: Re: mpslsi0 : Trying sleep, but thread marked as sleeping > prohibited >=20 > On Thursday, February 23, 2012 8:22:07 am Desai, Kashyap wrote: > > > > > -----Original Message----- > > > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > > > Sent: Thursday, February 23, 2012 2:55 PM > > > To: Desai, Kashyap > > > Cc: freebsd-scsi@freebsd.org; freebsd-stable; Justin T. Gibbs; > Kenneth > > > D. Merry; McConnell, Stephen > > > Subject: Re: mpslsi0 : Trying sleep, but thread marked as sleeping > > > prohibited > > > > > > On Thu, Feb 23, 2012 at 05:52:12AM +0530, Desai, Kashyap wrote: > > > > > > > > > > > > > -----Original Message----- > > > > > From: Konstantin Belousov [mailto:kostikbel@gmail.com] > > > > > Sent: Thursday, February 23, 2012 12:45 AM > > > > > To: Desai, Kashyap > > > > > Cc: freebsd-scsi@freebsd.org; freebsd-stable; Justin T. Gibbs; > > > > > Kenneth D. Merry; McConnell, Stephen > > > > > Subject: Re: mpslsi0 : Trying sleep, but thread marked as > sleeping > > > > > prohibited > > > > > > > > > > On Wed, Feb 22, 2012 at 07:36:42PM +0530, Desai, Kashyap wrote: > > > > > > Hi, > > > > > > > > > > > > I am doing some code changes in mps dirver. While working on > those > > > > > changes, I come to know about something which is new to me. > > > > > > Some expert help is required to clarify my doubt. > > > > > > > > > > > > 1. When any irq is register with FreeBSD OS, it sets " > > > TDP_NOSLEEPING" > > > > > > pflag. It means though irq in freebsd is treated as thread, We > > > > > > cannot > > > > > sleep in IRQ because of " "TDP_NOSLEEPING " set. > > > > > > 2. In mps driver we have below code snippet in ISR routine. > > > > > > > > > > > > > > > > > > mps_dprint(sc, MPS_TRACE, "%s\n", __func__); > > > > > > mps_lock(sc); > > > > > > mps_intr_locked(data); > > > > > > mps_unlock(sc); > > > > > > > > > > > > I wonder why there is no issue with above code ? Theoretical > we > > > > > > cannot sleep in ISR. (as explained in #1) Any thoughts ? > > > > > > > > > > > > > > > > > > 3. I recently added few place msleep() instead of DELAY in ISR > > > > > > context and I see " Trying sleep, but thread marked as > sleeping > > > prohibited". > > > > > > > > > > > FreeBSD has several basic ways to prevent a thread from > executing on > > > > > CPU. > > > > > They mostly fall into two categories: bounded sleep, sometimes > > > > > called blocking, and unbounded sleep, usually abbreviated as > sleep. > > > > > The bounded there refers to amount of code executed by other > thread > > > > > that hold resource preventing blocked thread from making a > progress. > > > > > > > > > > Examples of the blocking primitives are mutexes, rw locks and rm > > > locks. > > > > > The blocking is not counted as sleeping, so interrupt threads, > which > > > > > are designated as non-sleeping, still can lock mutexes. > > > > Thanks for the tech help. . > > > > > > > > As per you comment, So now I understood as "TDP_NOSLEEPING" is > only > > > > for unbounded sleep restriction. Just curious to know, What is a > > > > reason that thread can do blocking sleep but can't do unbounded > sleep > > > > ? Since technically we introduced sleeping restriction on > interrupt > > > > thread is to avoid starvation and that can be fit with either of > the > > > > sleep type. Is this not true ? > > > No, not to avoid starvation. > > > > > > The intent of the blocking primitives is to acquire resources for > > > limited amount of time. In other words, you never take a mutex for > > > undefinitely long computation process. On the other hand, msleep > sleep > > > usually has no limitations. > > > > I got same reply from Ed Schouten. I agree and understood your note. > Thanks > for poring knowledge on this area. > > _but_ only query is when thread take mutex, we don't know when it will > release. So holding time of mutex is really not known. > > In case of some bad code, where thread took mutex and not release > within > short time. This can eventually match upto msleep restriction as well. > > Do we have any checks that thread took long time holding mutext ? > Similar > to linux where spinlock has been not release in some specific time, they > dump > warnings with backtrace. >=20 > We don't allow code to do unbounded sleeps while holding mutexes either, > and > WITNESS warns about doing so. That ensures that barring an infinite > loop-type > bug, mutexes should be held for a bounded amount of time. Thanks. I understood this concept now. Really helpful conversation. >=20 > -- > John Baldwin From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 19:59:19 2012 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 C403F1065679 for ; Mon, 27 Feb 2012 19:59:19 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 771F38FC12 for ; Mon, 27 Feb 2012 19:59:19 +0000 (UTC) Received: by obbwc7 with SMTP id wc7so917668obb.13 for ; Mon, 27 Feb 2012 11:59:18 -0800 (PST) Received-SPF: pass (google.com: domain of nitroboost@gmail.com designates 10.60.3.167 as permitted sender) client-ip=10.60.3.167; Authentication-Results: mr.google.com; spf=pass (google.com: domain of nitroboost@gmail.com designates 10.60.3.167 as permitted sender) smtp.mail=nitroboost@gmail.com; dkim=pass header.i=nitroboost@gmail.com Received: from mr.google.com ([10.60.3.167]) by 10.60.3.167 with SMTP id d7mr6570818oed.20.1330372758955 (num_hops = 1); Mon, 27 Feb 2012 11:59:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Gc9/cylVcjzzQAnB+Ev0mRB2CoaS35+03Axx+mKVKLQ=; b=M00v3xdFUyWia1pvzo+Rq+NPgONMmE/SdIxvsOjK/T6Zz2aJBnEcx8g7MhdDtTeDF0 knsQedZyk7DvQUFpQkAtuGwmWhkRiwkFvAEIMHXiWgggZgk3yFXnwooElY3NUQxQhXZt 8rjOH1XKWcmbqTIfjIJsK2eC9U299q4P0FAH4= MIME-Version: 1.0 Received: by 10.60.3.167 with SMTP id d7mr5774590oed.20.1330372758879; Mon, 27 Feb 2012 11:59:18 -0800 (PST) Received: by 10.182.29.196 with HTTP; Mon, 27 Feb 2012 11:59:18 -0800 (PST) In-Reply-To: References: <4F450814.4020100@interlog.com> Date: Mon, 27 Feb 2012 12:59:18 -0700 Message-ID: From: Jason Wolfe To: "Desai, Kashyap" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-scsi@freebsd.org" , "McConnell, Stephen" Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver 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: Mon, 27 Feb 2012 19:59:19 -0000 On Wed, Feb 22, 2012 at 9:11 AM, Desai, Kashyap wro= te: > > >> -----Original Message----- >> From: Douglas Gilbert [mailto:dgilbert@interlog.com] >> Sent: Wednesday, February 22, 2012 8:52 PM >> To: Desai, Kashyap >> Cc: Jason Wolfe; freebsd-scsi@freebsd.org; McConnell, Stephen >> Subject: Re: LSI2008 controller clobbers first disk with new LSI mps >> driver >> >> On 12-02-22 03:39 AM, Desai, Kashyap wrote: >> > Here is a possible root cause of this issue. >> > >> > Enclosure which you are using in your setup (might be) not configured >> properly. >> > >> > You have Enclosure with 12 Slots + 1 SES Device. >> > See below detail from the log. >> > >> > =A0 =A0 EventDataLength: 5 >> > =A0 =A0 AckRequired: 0 >> > =A0 =A0 Event: SasEnclDeviceStatusChange (0x1d) >> > =A0 =A0 EventContext: 0x0 >> > =A0 =A0 EnclosureHandle: 0x2 >> > =A0 =A0 ReasonCode: Added >> > =A0 =A0 PhysicalPort: 0 >> > =A0 =A0 NumSlots: 13 >> > =A0 =A0 StartSlot: 0 >> > =A0 =A0 PhyBits: 0xff >> > >> > StartSlot is 0 in this case. >> > Correct behavior should be each device on your enclosure must have >> different slot number starting from 0 till 12. >> > I have doubt that SES device has not configured well and it is using >> slot-0 as default. This can create issue for actual device which is >> connected to slot-0. >> > So In your setup you will have slot-0 till slot-11 assigned for actual >> Phys of your enclosures and again slot-0 is assigned for SES device >> instead of Slot-12. >> >> No. SAS-2 expanders typically have an integral SES device on an >> expander _virtual_ phy (see SMP DISCOVER (LIST) response). Once >> you see that virtual phy flag the slot number is irrelevant. > > Doug, > > I need some more info so that I can understand your point better. > > I have one Enclosure setup on FreeBSD. Here is smp_discover output. (smp_= discover_list is failing for me) > > phy =A0 0: inaccessible (phy vacant) > =A0phy =A0 1: inaccessible (phy vacant) > =A0phy =A0 2: inaccessible (phy vacant) > =A0phy =A0 3: inaccessible (phy vacant) > =A0phy =A0 4:S:attached:[500605b012345888:03 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 5:S:attached:[500605b012345888:02 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 6:S:attached:[500605b012345888:01 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A0 7:S:attached:[500605b012345888:00 =A0i(SSP+STP+SMP)] =A06 Gbps > =A0phy =A012:D:attached:[5000c5003bc2c389:00 =A0t(SSP)] =A06 Gbps > =A0phy =A013:D:attached:[500000e116ee91e2:00 =A0t(SSP)] =A06 Gbps > =A0phy =A014:D:attached:[5000c5003bc308e5:00 =A0t(SSP)] =A06 Gbps > =A0phy =A015:D:attached:[5000c5003bc2f0d1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A016:D:attached:[5000c5003bc2ff3d:00 =A0t(SSP)] =A06 Gbps > =A0phy =A017:D:attached:[5000c5003bae5fdd:00 =A0t(SSP)] =A06 Gbps > =A0phy =A018:D:attached:[5000c5003bae5eb1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A019:D:attached:[5000c5003bc2d135:00 =A0t(SSP)] =A06 Gbps > =A0phy =A020:D:attached:[5000c5003baea36d:00 =A0t(SSP)] =A06 Gbps > =A0phy =A021:D:attached:[5000c5003bc2a8c9:00 =A0t(SSP)] =A06 Gbps > =A0phy =A022:D:attached:[5000c5003bc237a9:00 =A0t(SSP)] =A06 Gbps > =A0phy =A023:D:attached:[5000c5003bc2cec1:00 =A0t(SSP)] =A06 Gbps > =A0phy =A024:D:attached:[500000e01d92cb52:00 =A0t(SSP)] =A03 Gbps > =A0phy =A025:D:attached:[500000e01d74cfb2:00 =A0t(SSP)] =A03 Gbps > =A0phy =A026:D:attached:[500000e01d656052:00 =A0t(SSP)] =A03 Gbps > =A0phy =A027:D:attached:[500000e01d7cad52:00 =A0t(SSP)] =A03 Gbps > =A0phy =A028:D:attached:[500c04f2b64cdd1c:00 =A0t(SATA)] =A03 Gbps > =A0phy =A029:D:attached:[500c04f2b64cdd1d:00 =A0t(SATA)] =A03 Gbps > =A0phy =A030:D:attached:[500000e01d73c262:00 =A0t(SSP)] =A03 Gbps > =A0phy =A031:D:attached:[500000e01d536b22:00 =A0t(SSP)] =A03 Gbps > =A0phy =A032:D:attached:[500000e01d92cab2:00 =A0t(SSP)] =A03 Gbps > =A0phy =A033:D:attached:[500000e01afd8792:00 =A0t(SSP)] =A03 Gbps > =A0phy =A034:D:attached:[5000c5003bc30301:00 =A0t(SSP)] =A06 Gbps > =A0phy =A035:D:attached:[5000c5003bb09a69:00 =A0t(SSP)] =A06 Gbps > =A0phy =A036:D:attached:[500c04f2b64cdd3d:00 =A0V i(SSP) t(SSP)] =A06 Gbp= s =A0 <--- This has virtual phy set. > > What I understood from your explanation is if we have virt_phy field set,= we should not trust slot for that entry. > You are suggesting to use phy index instead of slot. Just for info: But h= ow to see Slot details mapping with phy ? > > ~ Kashyap > >> >> Doug Gilbert Kashyap, Let me know if there are any changes agreed upon, I'm happy to test out patches as this is affecting a large number of our machines. I can only imagine the same for others as they start to upgrade, as this is standard SuperMicro hardware. Thanks, Jason From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 27 23:41:38 2012 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 675751065674 for ; Mon, 27 Feb 2012 23:41:38 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id E12B98FC08 for ; Mon, 27 Feb 2012 23:41:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id B04EA204114; Tue, 28 Feb 2012 00:41:33 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ooKj2UBYPnus; Tue, 28 Feb 2012 00:41:32 +0100 (CET) Received: from [192.168.48.66] (unknown [206.126.85.117]) by smtp.infotech.no (Postfix) with ESMTPA id 1029620411E; Tue, 28 Feb 2012 00:41:30 +0100 (CET) Message-ID: <4F4C14A8.3050105@interlog.com> Date: Mon, 27 Feb 2012 18:41:28 -0500 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Jason Wolfe References: <4F450814.4020100@interlog.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-scsi@freebsd.org" , "Desai, Kashyap" , "McConnell, Stephen" Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 23:41:38 -0000 On 12-02-27 02:59 PM, Jason Wolfe wrote: > On Wed, Feb 22, 2012 at 9:11 AM, Desai, Kashyap wrote: >> >> >>> -----Original Message----- >>> From: Douglas Gilbert [mailto:dgilbert@interlog.com] >>> Sent: Wednesday, February 22, 2012 8:52 PM >>> To: Desai, Kashyap >>> Cc: Jason Wolfe; freebsd-scsi@freebsd.org; McConnell, Stephen >>> Subject: Re: LSI2008 controller clobbers first disk with new LSI mps >>> driver >>> >>> On 12-02-22 03:39 AM, Desai, Kashyap wrote: >>>> Here is a possible root cause of this issue. >>>> >>>> Enclosure which you are using in your setup (might be) not configured >>> properly. >>>> >>>> You have Enclosure with 12 Slots + 1 SES Device. >>>> See below detail from the log. >>>> >>>> EventDataLength: 5 >>>> AckRequired: 0 >>>> Event: SasEnclDeviceStatusChange (0x1d) >>>> EventContext: 0x0 >>>> EnclosureHandle: 0x2 >>>> ReasonCode: Added >>>> PhysicalPort: 0 >>>> NumSlots: 13 >>>> StartSlot: 0 >>>> PhyBits: 0xff >>>> >>>> StartSlot is 0 in this case. >>>> Correct behavior should be each device on your enclosure must have >>> different slot number starting from 0 till 12. >>>> I have doubt that SES device has not configured well and it is using >>> slot-0 as default. This can create issue for actual device which is >>> connected to slot-0. >>>> So In your setup you will have slot-0 till slot-11 assigned for actual >>> Phys of your enclosures and again slot-0 is assigned for SES device >>> instead of Slot-12. >>> >>> No. SAS-2 expanders typically have an integral SES device on an >>> expander _virtual_ phy (see SMP DISCOVER (LIST) response). Once >>> you see that virtual phy flag the slot number is irrelevant. >> >> Doug, >> >> I need some more info so that I can understand your point better. >> >> I have one Enclosure setup on FreeBSD. Here is smp_discover output. (smp_discover_list is failing for me) >> >> phy 0: inaccessible (phy vacant) >> phy 1: inaccessible (phy vacant) >> phy 2: inaccessible (phy vacant) >> phy 3: inaccessible (phy vacant) >> phy 4:S:attached:[500605b012345888:03 i(SSP+STP+SMP)] 6 Gbps >> phy 5:S:attached:[500605b012345888:02 i(SSP+STP+SMP)] 6 Gbps >> phy 6:S:attached:[500605b012345888:01 i(SSP+STP+SMP)] 6 Gbps >> phy 7:S:attached:[500605b012345888:00 i(SSP+STP+SMP)] 6 Gbps >> phy 12:D:attached:[5000c5003bc2c389:00 t(SSP)] 6 Gbps >> phy 13:D:attached:[500000e116ee91e2:00 t(SSP)] 6 Gbps >> phy 14:D:attached:[5000c5003bc308e5:00 t(SSP)] 6 Gbps >> phy 15:D:attached:[5000c5003bc2f0d1:00 t(SSP)] 6 Gbps >> phy 16:D:attached:[5000c5003bc2ff3d:00 t(SSP)] 6 Gbps >> phy 17:D:attached:[5000c5003bae5fdd:00 t(SSP)] 6 Gbps >> phy 18:D:attached:[5000c5003bae5eb1:00 t(SSP)] 6 Gbps >> phy 19:D:attached:[5000c5003bc2d135:00 t(SSP)] 6 Gbps >> phy 20:D:attached:[5000c5003baea36d:00 t(SSP)] 6 Gbps >> phy 21:D:attached:[5000c5003bc2a8c9:00 t(SSP)] 6 Gbps >> phy 22:D:attached:[5000c5003bc237a9:00 t(SSP)] 6 Gbps >> phy 23:D:attached:[5000c5003bc2cec1:00 t(SSP)] 6 Gbps >> phy 24:D:attached:[500000e01d92cb52:00 t(SSP)] 3 Gbps >> phy 25:D:attached:[500000e01d74cfb2:00 t(SSP)] 3 Gbps >> phy 26:D:attached:[500000e01d656052:00 t(SSP)] 3 Gbps >> phy 27:D:attached:[500000e01d7cad52:00 t(SSP)] 3 Gbps >> phy 28:D:attached:[500c04f2b64cdd1c:00 t(SATA)] 3 Gbps >> phy 29:D:attached:[500c04f2b64cdd1d:00 t(SATA)] 3 Gbps >> phy 30:D:attached:[500000e01d73c262:00 t(SSP)] 3 Gbps >> phy 31:D:attached:[500000e01d536b22:00 t(SSP)] 3 Gbps >> phy 32:D:attached:[500000e01d92cab2:00 t(SSP)] 3 Gbps >> phy 33:D:attached:[500000e01afd8792:00 t(SSP)] 3 Gbps >> phy 34:D:attached:[5000c5003bc30301:00 t(SSP)] 6 Gbps >> phy 35:D:attached:[5000c5003bb09a69:00 t(SSP)] 6 Gbps >> phy 36:D:attached:[500c04f2b64cdd3d:00 V i(SSP) t(SSP)] 6 Gbps<--- This has virtual phy set. >> >> What I understood from your explanation is if we have virt_phy field set, we should not trust slot for that entry. >> You are suggesting to use phy index instead of slot. Just for info: But how to see Slot details mapping with phy ? Kashyap, I haven't written a SAS discover algorithm but there must be plenty of examples out there. One way to do it is to find all the phy_ids attached to targets, in this case there are SAS (SSP) and SATA targets. Each SATA target phy_id will correspond to one SATA disk (or could be an ATAPI device (e.g. DVD/BD player)). The SSP targets are a bit trickier because two (or more) phys could be connected to the same target (either a wide port or multiple (target) ports). With a wide port each component phy has the same attached SAS address (so above you have a wide initiator port (phy ids 4,5,6,7) but no wide target ports). If a SAS disk has multiple target ports connected, FreeBSD probably has a device node for each. So for each SCSI (SSP) target port you need a REPORT LUNS command issued on LUN 0 (or the REPORT LUNS well known logical unit) to find the LUs it contains. A device node is created for each LU. Anyway I'm sure many folks in LSI know the SAS discover process better than I do. Ask them :-) Surely most of the above is already done in your HBA's firmware. BTW I don't think slot numbers are reliable and don't apply to things on virtual phys so they will just cause you problems when used in the discover process, as this thread attests. The BIOS on LSI's HBAs does a discover process but is only interested in bootable devices so SES devices don't appear. Doug Gilbert > Kashyap, > > Let me know if there are any changes agreed upon, I'm happy to test > out patches as this is affecting a large number of our machines. I > can only imagine the same for others as they start to upgrade, as this > is standard SuperMicro hardware. > > Thanks, > Jason > From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 28 00:05:11 2012 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 B59B71065675 for ; Tue, 28 Feb 2012 00:05:11 +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 7E9B78FC0A for ; Tue, 28 Feb 2012 00:05:11 +0000 (UTC) Received: from [172.16.135.105] (lportal.in1.lcl [172.16.1.9]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q1RNnShp042958 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 27 Feb 2012 15:49:28 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4F4C1683.8000107@feral.com> Date: Mon, 27 Feb 2012 15:49:23 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4F450814.4020100@interlog.com> <4F4C14A8.3050105@interlog.com> In-Reply-To: <4F4C14A8.3050105@interlog.com> 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]); Mon, 27 Feb 2012 15:49:28 -0800 (PST) Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2012 00:05:11 -0000 See the opensolaris pmcs driver for one example of SAS discovery in software See also linux/pm8001 and sas layer ass wel From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 28 08:05:18 2012 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 54B21106566B for ; Tue, 28 Feb 2012 08:05:18 +0000 (UTC) (envelope-from cstamas@digitus.itk.ppke.hu) Received: from jugisgw.ppke.hu (mailgw.ppke.hu [193.225.109.43]) by mx1.freebsd.org (Postfix) with ESMTP id 054628FC16 for ; Tue, 28 Feb 2012 08:05:17 +0000 (UTC) Received: from jugisgw.ppke.hu (localhost.localdomain [127.0.0.1]) by jugisgw.ppke.hu (Postfix) with ESMTP id AFD4C40146CB; Tue, 28 Feb 2012 09:05:25 +0100 (CET) X-PPKE-MailScanner-Watermark: 1331021122.31855@rtkq7dApJLLLR1m72EBBpQ X-PPKE-MailScanner-From: cstamas@digitus.itk.ppke.hu X-PPKE-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, pont=0, szukseges 5, autolearn=disabled) X-PPKE-MailScanner: Found to be clean X-PPKE-MailScanner-ID: 1S2I3l-00081H-P0 Received: from rivendell.itk.ppke.hu (rivendell.itk.ppke.hu [193.225.109.193]) by jugisgw.ppke.hu (Postfix) with ESMTP id AE95B40146D3; Tue, 28 Feb 2012 09:05:21 +0100 (CET) Received: by rivendell.itk.ppke.hu (Postfix, from userid 1000) id EAAD934B86; Tue, 28 Feb 2012 09:05:11 +0100 (CET) Date: Tue, 28 Feb 2012 09:05:11 +0100 From: Csillag Tamas To: Jan Mikkelsen Message-ID: <20120228080511.GN29886@rivendell> References: <20120223235932.GB19927@rivendell> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Operating-System: Gnu/Linux X-PPKE-NOSPAM: I promise, I will never let anything happen to you. Nemo. X-PGP-Key: http://digitus.itk.ppke.hu/~cstamas/cstamas.pgp User-Agent: Mutt/1.5.20 (2009-06-14) Content-Transfer-Encoding: quoted-printable Cc: freebsd-scsi@freebsd.org Subject: Re: mfi timeout issues and patch that seems to work (PERC H800) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Csillag Tamas List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2012 08:05:18 -0000 On Sat, Feb 25, 2012 at 12:04:05PM +1100, Jan Mikkelsen wrote: > On 24/02/2012, at 10:59 AM, Csillag Tamas wrote: > > Hi, > >=20 > > I had the same issues with the Perc H800 controller as it is describe= d > > here:=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/140416 > > (Just for google I include the error here: > > mfi0: COMMAND 0xffffff80009c4b90 TIMEOUT AFTER 41 SECONDS) > > [ =E2=80=A6 ] > > however getting and compiling the newest kernel did NOT fix it for me= . > > Issuing commands with mfiutils still fixed the hang and everything > > returned to normal. > >=20 > > It seems that intensive read triggers the issue, but if you have writ= e > > concurrently you are fine (mostly). Restarting rsync is ideal for > > triggering this buggy condition. > >=20 > > I tried to poke around in the source code and in the end tweaked the > > patch (seen here before > > http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.htm= l): > >=20 > > replacing > > (void)sc->mfi_read_fw_status(sc); > > with > > mfi_get_controller_info(sc); > > around line 933 > >=20 > > and after testing it for a day it seems to be solid. > > (The original patch did not help me.) > >=20 > > Can someone expert in the topic can confirm if any of this is correct= ? >=20 > The default value for hw.mfi.msi is 0. I had to set it to 1 in > /boot/loader.conf when using a 9261-8i controller. It might be worth > retesting with that setting and the standard kernel. I am not sure if I will have enough time for this (others starts to work on this machine), but will make a try. Thanks Regards, cstamas --=20 CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 28 23:15:42 2012 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 3A974106564A for ; Tue, 28 Feb 2012 23:15:42 +0000 (UTC) (envelope-from jwd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD7B8FC0C for ; Tue, 28 Feb 2012 23:15:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1SNFgKS050090 for ; Tue, 28 Feb 2012 23:15:42 GMT (envelope-from jwd@freefall.freebsd.org) Received: (from jwd@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1SNFfkw050089 for freebsd-scsi@freebsd.org; Tue, 28 Feb 2012 23:15:41 GMT (envelope-from jwd) Date: Tue, 28 Feb 2012 23:15:41 +0000 From: John To: freebsd-scsi@freebsd.org Message-ID: <20120228231541.GA14736@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: System Hang / kernel panic with new mps driver 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: Tue, 28 Feb 2012 23:15:42 -0000 Hi Folks, I realize there has been some discussion going on related to the new mps driver recently. Today I caught a kernel panic when we lost a multipath channel and then fixed it (replaced the cable). The complete dmesg from a system boot with hw.mps.debug_level=0xd (it's large): http://people.freebsd.org/~jwd/mpsdmesg.txt Kernel is 9-stable: r231864M /usr/obj/usr/src.2012-02-17_01.26.11/sys/ZFS When the cable was replaced, the system started throwing messages to the console quite fast: Feb 28 18:33:24 testsys kernel: mps1: mpssas_alloc_tm freezing simq Feb 28 18:33:24 testsys kernel: mps1: timedout cm 0xffffff800136b240 allocated tm 0xffffff800132f528 Feb 28 18:33:24 testsys kernel: mps1: mpssas_scsiio_timeout checking sc 0xffffff800131a000 cm 0xffffff800135ee38 Feb 28 18:33:24 testsys kernel: (xpt0:mps1:0:67:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 d 0 0 length 13 SMID 776 completed timedout cm 0xffffff800136b240 ccb 0xfffffe00612f 4800 during recovery ioc 8048 s(noperiph:mps1:0:67:0): SMID 29 abort TaskMID 776 status 0x0 code 0x0 count 1 Feb 28 18:33:24 testsys kernel: (noperiph:mps1:0:67:0): SMID 29 finished recovery after aborting TaskMID 776 Feb 28 18:33:24 testsys kernel: mps1: mpssas_free_tm releasing simq Feb 28 18:33:24 testsys kernel: (xpt0:mps1:0:67:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 d 0 0 length 13 SMID 623 command timeout cm 0xffffff800135ee38 ccb 0xfffffe12d189680 0 Feb 28 18:33:24 testsys kernel: mps1: mpssas_alloc_tm freezing simq Feb 28 18:33:24 testsys kernel: mps1: timedout cm 0xffffff800135ee38 allocated tm 0xffffff800132f670 Feb 28 18:33:24 testsys kernel: (xpt0:mps1:0:67:0): SERVICE ACTION IN(16). CDB: 9e 10 0 0 0 0 0 0 0 0 0 0 0 d 0 0 length 13 SMID 623 completed timedout cm 0xf Feb 28 18:33:24 testsys kernel: fffff800135ee38 ccb 0xfffffe12d1896800 during recovery ioc 8048 s(noperiph:mps1:0:67:0): SMID 30 abort TaskMID 623 status 0x0 code 0x0 count 1 Feb 28 18:33:24 testsys kernel: (noperiph:mps1:0:67:0): SMID 30 finished recovery after aborting TaskMID 623 Feb 28 18:33:24 testsys kernel: mps1: mpssas_free_tm releasing simq Many, many of the above.. eventually followed by: Feb 28 18:35:07 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0102 to persistent table because there is no free space available Feb 28 18:35:07 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0104 to persistent table because there is no free space available Feb 28 18:35:07 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0105 to persistent table because there is no free space available ... Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0132 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0133 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0134 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0135 to persistent table because there is no free space available more mps CDB messages, and then Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0136 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0137 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0138 to persistent table because there is no free space available ... Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0150 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0151 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0152 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0153 to persistent table because there is no free space available Feb 28 18:35:08 testsys kernel: _mapping_add_new_device: failed to add the device with handle 0x0155 to persistent table because there is no free space available At this point the kernel panic'd. (typed from a phone pic - sorry) Fatal trap 12: page fault while in kernel mode ... Stopped at xpt_compile_path+0x87: cmpl 0x50(%rbx),%r11d bt xpt_compile_path() at xpt_compile_path+0x87 xpt_create_path() at xpt_create_path+0x66 mps_rescan_done() at mpssas_rescan_done+0x16a camisr_runqueue() at camisr_runqueue+0x63 intr_event_execute_handlers() at intr_event_execute_handlers+0x104 ithread_loop() at ithread_loop+0xa4 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe Not sure if it makes a difference, but during a normal (clean boot), the above 'failed to add the device' messages show up 160 times. This doesn't appear to be a #define value, but a 'fact' from the adapter. Since all the shelves are dual attached and every disk shows up twice, could this make a difference to the initialization logic? (ses devices show up twice also). Any thoughts are welcome. The system is available for testing. Thanks, John From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 29 04:22:53 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 15056106566B for ; Wed, 29 Feb 2012 04:22:53 +0000 (UTC) (envelope-from bsalinux@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id B6DE68FC16 for ; Wed, 29 Feb 2012 04:22:52 +0000 (UTC) Received: by qao25 with SMTP id 25so2531294qao.13 for ; Tue, 28 Feb 2012 20:22:52 -0800 (PST) Received-SPF: pass (google.com: domain of bsalinux@gmail.com designates 10.224.196.66 as permitted sender) client-ip=10.224.196.66; Authentication-Results: mr.google.com; spf=pass (google.com: domain of bsalinux@gmail.com designates 10.224.196.66 as permitted sender) smtp.mail=bsalinux@gmail.com; dkim=pass header.i=bsalinux@gmail.com Received: from mr.google.com ([10.224.196.66]) by 10.224.196.66 with SMTP id ef2mr521767qab.64.1330489372087 (num_hops = 1); Tue, 28 Feb 2012 20:22:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SXu1c/FcDeKfbv8kKNYzKSlhk7IxRlw5qFFcLT8eNBw=; b=vj5ap/geWXRRNBmVTjI76YmThCb5qQ+1qAewvmaRj3w1GmMz9vx3FoddvtJxQKYAcX RpCUZUTl/b9asQmHxczvEJ/R5GOHjXtw3T7ABEq+j6oio7uCWi+cMBzkjx59lfPybMFV zG/HMmBX7won1my0x5+exsDXQYDMuJJjXn1gs= MIME-Version: 1.0 Received: by 10.224.196.66 with SMTP id ef2mr428159qab.64.1330489372016; Tue, 28 Feb 2012 20:22:52 -0800 (PST) Received: by 10.229.211.80 with HTTP; Tue, 28 Feb 2012 20:22:51 -0800 (PST) In-Reply-To: References: <4F494676.2000909@fuckner.net> <4F49EA56.2010101@mullet.se> Date: Tue, 28 Feb 2012 20:22:51 -0800 Message-ID: From: "bsalinux@gmail.com" To: "Desai, Kashyap" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-scsi@freebsd.org Subject: Re: IBM M1015 support 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, 29 Feb 2012 04:22:53 -0000 Kashyap, Where can I find the current version of mfi driver from LSI? One of the threads pointed at http://www.lsi.com/downloads/Public/MegaRAID%20Common%20Files/4.23_FreeBSD_SAS_Driver.zip but looks like it no longer exist. Supposedly this driver supports IBM ServeRAID M1015. I looked at the downloads section on individual product pages but couldn't find it there. Any help would be appreciated. Thanks. On Sun, Feb 26, 2012 at 6:57 PM, Desai, Kashyap wrote: > YES, LSI has plan to do mfi drivers changes in order to fix basic need for customers. > > I am not sure which freebsd version will be the first one to get those changes in. > As of now I have this much information to share so wait for some more time to get more info. > > ~ Kashyap From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 29 16:38:35 2012 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 11AE61065679 for ; Wed, 29 Feb 2012 16:38:35 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog119.obsmtp.com (na3sys009aog119.obsmtp.com [74.125.149.246]) by mx1.freebsd.org (Postfix) with ESMTP id 556078FC1C for ; Wed, 29 Feb 2012 16:38:34 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob119.postini.com ([74.125.148.12]) with SMTP ID DSNKT05UiVUu75SGaL0+GhwFIyyornuLZdL4@postini.com; Wed, 29 Feb 2012 08:38:34 PST Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 29 Feb 2012 11:43:04 -0500 Received: from inbexch02.lsi.com (135.36.98.40) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 29 Feb 2012 11:38:32 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Wed, 29 Feb 2012 22:08:28 +0530 From: "Desai, Kashyap" To: "dgilbert@interlog.com" , Jason Wolfe Date: Wed, 29 Feb 2012 22:08:25 +0530 Thread-Topic: LSI2008 controller clobbers first disk with new LSI mps driver Thread-Index: Acz1qVrkiusUZ1ojROe2toFMjfTklwBVq20w Message-ID: References: <4F450814.4020100@interlog.com> <4F4C14A8.3050105@interlog.com> In-Reply-To: <4F4C14A8.3050105@interlog.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" , "McConnell, Stephen" Subject: RE: LSI2008 controller clobbers first disk with new LSI mps driver 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, 29 Feb 2012 16:38:35 -0000 Hi Jason, I have started discussion with LSI internal folks to get better clarity on = this issue. Since our key person is on vacation, we may get clarity on this= next week. I cannot provide some temporary workaround in upstream(because this is agai= nst our design), but if you want to use for your environment, I can provide= you some temporary patch. Doug, Thanks for providing your view and I have convey this to our architect. ~ Kashyap > -----Original Message----- > From: Douglas Gilbert [mailto:dgilbert@interlog.com] > Sent: Tuesday, February 28, 2012 5:11 AM > To: Jason Wolfe > Cc: Desai, Kashyap; freebsd-scsi@freebsd.org; McConnell, Stephen > Subject: Re: LSI2008 controller clobbers first disk with new LSI mps > driver >=20 > On 12-02-27 02:59 PM, Jason Wolfe wrote: > > On Wed, Feb 22, 2012 at 9:11 AM, Desai, Kashyap > wrote: > >> > >> > >>> -----Original Message----- > >>> From: Douglas Gilbert [mailto:dgilbert@interlog.com] > >>> Sent: Wednesday, February 22, 2012 8:52 PM > >>> To: Desai, Kashyap > >>> Cc: Jason Wolfe; freebsd-scsi@freebsd.org; McConnell, Stephen > >>> Subject: Re: LSI2008 controller clobbers first disk with new LSI mps > >>> driver > >>> > >>> On 12-02-22 03:39 AM, Desai, Kashyap wrote: > >>>> Here is a possible root cause of this issue. > >>>> > >>>> Enclosure which you are using in your setup (might be) not > configured > >>> properly. > >>>> > >>>> You have Enclosure with 12 Slots + 1 SES Device. > >>>> See below detail from the log. > >>>> > >>>> EventDataLength: 5 > >>>> AckRequired: 0 > >>>> Event: SasEnclDeviceStatusChange (0x1d) > >>>> EventContext: 0x0 > >>>> EnclosureHandle: 0x2 > >>>> ReasonCode: Added > >>>> PhysicalPort: 0 > >>>> NumSlots: 13 > >>>> StartSlot: 0 > >>>> PhyBits: 0xff > >>>> > >>>> StartSlot is 0 in this case. > >>>> Correct behavior should be each device on your enclosure must have > >>> different slot number starting from 0 till 12. > >>>> I have doubt that SES device has not configured well and it is > using > >>> slot-0 as default. This can create issue for actual device which is > >>> connected to slot-0. > >>>> So In your setup you will have slot-0 till slot-11 assigned for > actual > >>> Phys of your enclosures and again slot-0 is assigned for SES device > >>> instead of Slot-12. > >>> > >>> No. SAS-2 expanders typically have an integral SES device on an > >>> expander _virtual_ phy (see SMP DISCOVER (LIST) response). Once > >>> you see that virtual phy flag the slot number is irrelevant. > >> > >> Doug, > >> > >> I need some more info so that I can understand your point better. > >> > >> I have one Enclosure setup on FreeBSD. Here is smp_discover output. > (smp_discover_list is failing for me) > >> > >> phy 0: inaccessible (phy vacant) > >> phy 1: inaccessible (phy vacant) > >> phy 2: inaccessible (phy vacant) > >> phy 3: inaccessible (phy vacant) > >> phy 4:S:attached:[500605b012345888:03 i(SSP+STP+SMP)] 6 Gbps > >> phy 5:S:attached:[500605b012345888:02 i(SSP+STP+SMP)] 6 Gbps > >> phy 6:S:attached:[500605b012345888:01 i(SSP+STP+SMP)] 6 Gbps > >> phy 7:S:attached:[500605b012345888:00 i(SSP+STP+SMP)] 6 Gbps > >> phy 12:D:attached:[5000c5003bc2c389:00 t(SSP)] 6 Gbps > >> phy 13:D:attached:[500000e116ee91e2:00 t(SSP)] 6 Gbps > >> phy 14:D:attached:[5000c5003bc308e5:00 t(SSP)] 6 Gbps > >> phy 15:D:attached:[5000c5003bc2f0d1:00 t(SSP)] 6 Gbps > >> phy 16:D:attached:[5000c5003bc2ff3d:00 t(SSP)] 6 Gbps > >> phy 17:D:attached:[5000c5003bae5fdd:00 t(SSP)] 6 Gbps > >> phy 18:D:attached:[5000c5003bae5eb1:00 t(SSP)] 6 Gbps > >> phy 19:D:attached:[5000c5003bc2d135:00 t(SSP)] 6 Gbps > >> phy 20:D:attached:[5000c5003baea36d:00 t(SSP)] 6 Gbps > >> phy 21:D:attached:[5000c5003bc2a8c9:00 t(SSP)] 6 Gbps > >> phy 22:D:attached:[5000c5003bc237a9:00 t(SSP)] 6 Gbps > >> phy 23:D:attached:[5000c5003bc2cec1:00 t(SSP)] 6 Gbps > >> phy 24:D:attached:[500000e01d92cb52:00 t(SSP)] 3 Gbps > >> phy 25:D:attached:[500000e01d74cfb2:00 t(SSP)] 3 Gbps > >> phy 26:D:attached:[500000e01d656052:00 t(SSP)] 3 Gbps > >> phy 27:D:attached:[500000e01d7cad52:00 t(SSP)] 3 Gbps > >> phy 28:D:attached:[500c04f2b64cdd1c:00 t(SATA)] 3 Gbps > >> phy 29:D:attached:[500c04f2b64cdd1d:00 t(SATA)] 3 Gbps > >> phy 30:D:attached:[500000e01d73c262:00 t(SSP)] 3 Gbps > >> phy 31:D:attached:[500000e01d536b22:00 t(SSP)] 3 Gbps > >> phy 32:D:attached:[500000e01d92cab2:00 t(SSP)] 3 Gbps > >> phy 33:D:attached:[500000e01afd8792:00 t(SSP)] 3 Gbps > >> phy 34:D:attached:[5000c5003bc30301:00 t(SSP)] 6 Gbps > >> phy 35:D:attached:[5000c5003bb09a69:00 t(SSP)] 6 Gbps > >> phy 36:D:attached:[500c04f2b64cdd3d:00 V i(SSP) t(SSP)] 6 Gbps<- > -- This has virtual phy set. > >> > >> What I understood from your explanation is if we have virt_phy field > set, we should not trust slot for that entry. > >> You are suggesting to use phy index instead of slot. Just for info: > But how to see Slot details mapping with phy ? >=20 > Kashyap, > I haven't written a SAS discover algorithm but there > must be plenty of examples out there. One way to do it > is to find all the phy_ids attached to targets, in this > case there are SAS (SSP) and SATA targets. Each SATA > target phy_id will correspond to one SATA disk (or could be an > ATAPI device (e.g. DVD/BD player)). The SSP targets are a > bit trickier because two (or more) phys could be connected > to the same target (either a wide port or multiple (target) > ports). With a wide port each component phy has the same > attached SAS address (so above you have a wide initiator > port (phy ids 4,5,6,7) but no wide target ports). If a > SAS disk has multiple target ports connected, FreeBSD > probably has a device node for each. So for each SCSI (SSP) > target port you need a REPORT LUNS command issued on LUN 0 > (or the REPORT LUNS well known logical unit) to find the > LUs it contains. A device node is created for each LU. >=20 > Anyway I'm sure many folks in LSI know the SAS discover > process better than I do. Ask them :-) Surely most of > the above is already done in your HBA's firmware. >=20 >=20 > BTW I don't think slot numbers are reliable and don't apply > to things on virtual phys so they will just cause you > problems when used in the discover process, as this thread > attests. The BIOS on LSI's HBAs does a discover process > but is only interested in bootable devices so SES devices > don't appear. >=20 >=20 > Doug Gilbert >=20 > > Kashyap, > > > > Let me know if there are any changes agreed upon, I'm happy to test > > out patches as this is affecting a large number of our machines. I > > can only imagine the same for others as they start to upgrade, as this > > is standard SuperMicro hardware. > > > > Thanks, > > Jason > > From owner-freebsd-scsi@FreeBSD.ORG Thu Mar 1 20:49:00 2012 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 1998D1065752 for ; Thu, 1 Mar 2012 20:49:00 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8E88FC12 for ; Thu, 1 Mar 2012 20:48:59 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 247443137 for freebsd-scsi@freebsd.org; Thu, 01 Mar 2012 21:48:57 +0100 From: Hans Petter Selasky To: freebsd-scsi@freebsd.org Date: Thu, 1 Mar 2012 21:47:17 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <201202262206.08378.hselasky@c2i.net> In-Reply-To: <201202262206.08378.hselasky@c2i.net> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203012147.17325.hselasky@c2i.net> Subject: Re: CAM layer gets stuck when sim->refcount > 0 at UMASS detach (10-current) 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: Thu, 01 Mar 2012 20:49:00 -0000 On Sunday 26 February 2012 22:06:08 Hans Petter Selasky wrote: > Hi, > > When running a stress test on a USB mass storage device, the CAM layer will > eventually block at detach, because the refcount is not going towards zero > on the SIM structure. > Hi, This issue is now solved: http://svn.freebsd.org/changeset/base/232358 --HPS From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 2 21:55:24 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CB43106566C for ; Fri, 2 Mar 2012 21:55:24 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id AF4C18FC12 for ; Fri, 2 Mar 2012 21:55:23 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q22LivUV063111 for ; Fri, 2 Mar 2012 13:44:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1330724697; bh=kSzpgA3qK+B9Nml/9URjHwgD/+Aex+1WNu89VIPkWTo=; h=Subject:From:Reply-To:To:Content-Type:Date:Message-ID: Mime-Version; b=ClRXxRTf0iVcO+joh7Mhtv6LUvRJqRGx1H2SAzwotr1l9zc8wVlC7/1e4054Lz0YW 0ndTgtnSGlDDl9f4bzwCxQIzTJnGRrZOZPMIhk6lc3vWjQ5WTxL9R2HP6c2ij8Os3p /DmJRh88/rziTOgX/j7QVsMNXdL/TVB6IMl9l/cg= From: Sean Bruno To: scsi@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-AZbfbJ8JHTe04VfXL5F2" Date: Fri, 02 Mar 2012 13:44:57 -0800 Message-ID: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: Subject: [patch] Add New PCI ID to mfi(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sbruno@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 21:55:24 -0000 --=-AZbfbJ8JHTe04VfXL5F2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable New megaraid SAS card from Dell coming down the pipe. I think this is the right thing to do. --- //depot/yahoo/ybsd_7/src/sys/dev/mfi/mfi_pci.c 2011-09-16 22:47:30.000000000 0000 +++ /home/seanbru/ybsd_7/src/sys/dev/mfi/mfi_pci.c 2011-09-16 22:47:30.000000000 0000 @@ -123,6 +123,7 @@ {0x1000, 0x0079, 0x1028, 0x1f17, MFI_FLAGS_GEN2, "Dell PERC H700 Integrated"}, {0x1000, 0x0079, 0x1028, 0x1f18, MFI_FLAGS_GEN2, "Dell PERC H700 Modular"}, {0x1000, 0x0079, 0x1028, 0x1f19, MFI_FLAGS_GEN2, "Dell PERC H700"}, + {0x1000, 0x005b, 0x1028, 0x1f34, MFI_FLAGS_GEN2, "Dell PERC H710P Mini"}, {0x1000, 0x0079, 0x1028, 0x1f1b, MFI_FLAGS_GEN2, "Dell PERC H800"}, {0x1000, 0x0079, 0x1028, 0xffff, MFI_FLAGS_GEN2, "Dell PERC Gen2"}, {0x1000, 0x0079, 0xffff, 0xffff, MFI_FLAGS_GEN2, "LSI MegaSAS Gen2"}, --=-AZbfbJ8JHTe04VfXL5F2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAABAgAGBQJPUT9ZAAoJEL2UHwafTLtORjEH/R55HyuZSSduBKrddbi3XkKz u3AMgVZgao7q+ZmGD1yzQRbY1/UwL6VLWaQ8b7nHql5DoPNI1Wbg0cWr4t+jycog hrVg5WuVPCFdadzSGn3bUXOTT3GkNHcIFjb/P80t4q5ozzvqJ906N0rMYOCOLxrD 5pLQWLQxx680jImIrM86FJBGvZwdVZ3AMxu07VIV8VeDRkTWBHCH8h9co1w7L68E ujv5ErHtBhRM27ofJ6dOfIU+7AGMbya6RvgNE87hyhMNqzhctfri+eZmecaq0rrz j28OPV736S8lIdtNyUX7dn2mgpMeNPlsrP0ewZg1H8BoxFFn+VpZTG1a+34/UCs= =2RHc -----END PGP SIGNATURE----- --=-AZbfbJ8JHTe04VfXL5F2-- From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 2 22:16:28 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0192C1065673; Fri, 2 Mar 2012 22:16:28 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id BE7BA8FC12; Fri, 2 Mar 2012 22:16:27 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q22M5qnC061919; Fri, 2 Mar 2012 15:05:52 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q22M5qGJ061918; Fri, 2 Mar 2012 15:05:52 -0700 (MST) (envelope-from ken) Date: Fri, 2 Mar 2012 15:05:52 -0700 From: "Kenneth D. Merry" To: sbruno@freebsd.org Message-ID: <20120302220551.GA60828@nargothrond.kdm.org> References: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> User-Agent: Mutt/1.4.2i Cc: scsi@freebsd.org Subject: Re: [patch] Add New PCI ID to mfi(4) 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: Fri, 02 Mar 2012 22:16:28 -0000 On Fri, Mar 02, 2012 at 13:44:57 -0800, Sean Bruno wrote: > New megaraid SAS card from Dell coming down the pipe. I think this is > the right thing to do. In order for that to work correctly, at least with a GENERIC kernel, you'll need SVN rev 232411. (Just committed.) The mpt(4) driver was masking off the bottom bit of the PCI device ID, and causing it to attach to some MegaRAID controllers. > > --- //depot/yahoo/ybsd_7/src/sys/dev/mfi/mfi_pci.c 2011-09-16 > 22:47:30.000000000 0000 > +++ /home/seanbru/ybsd_7/src/sys/dev/mfi/mfi_pci.c 2011-09-16 > 22:47:30.000000000 0000 > @@ -123,6 +123,7 @@ > {0x1000, 0x0079, 0x1028, 0x1f17, MFI_FLAGS_GEN2, "Dell PERC > H700 Integrated"}, > {0x1000, 0x0079, 0x1028, 0x1f18, MFI_FLAGS_GEN2, "Dell PERC > H700 Modular"}, > {0x1000, 0x0079, 0x1028, 0x1f19, MFI_FLAGS_GEN2, "Dell PERC > H700"}, > + {0x1000, 0x005b, 0x1028, 0x1f34, MFI_FLAGS_GEN2, "Dell PERC > H710P Mini"}, > {0x1000, 0x0079, 0x1028, 0x1f1b, MFI_FLAGS_GEN2, "Dell PERC > H800"}, > {0x1000, 0x0079, 0x1028, 0xffff, MFI_FLAGS_GEN2, "Dell PERC > Gen2"}, > {0x1000, 0x0079, 0xffff, 0xffff, MFI_FLAGS_GEN2, "LSI MegaSAS > Gen2"}, > Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 2 22:20:48 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3CE61065674; Fri, 2 Mar 2012 22:20:48 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id B5D8C8FC17; Fri, 2 Mar 2012 22:20:48 +0000 (UTC) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 7DC82110D3; Fri, 2 Mar 2012 14:20:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1330726848; bh=stoeHwkYoCILxRBee7AldpysvYlNCsjKPxDTpWz/UpU=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=BJD7XBUIVzomoPkd94jPSzpqe/LxY1fnRqONQOKMQahUiQd9+pn7gCvAs5AgZANPi wSvIzwziK59rgsI4Cez1zR/4PJjhSFO3z5HXZW4MS0UE/MX25gNEfEVGxAnaL78YaM RqqZ7lsWo1N0Uc3sgehy3mIxzmNLfRkrdwJtU2LI= Message-ID: <4F5147BF.4050404@delphij.net> Date: Fri, 02 Mar 2012 14:20:47 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: sbruno@freebsd.org References: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> In-Reply-To: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: d@delphij.net, Sean Bruno , scsi@freebsd.org Subject: Re: [patch] Add New PCI ID to mfi(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 22:20:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Sean, On 03/02/12 13:44, Sean Bruno wrote: > New megaraid SAS card from Dell coming down the pipe. I think this > is the right thing to do. These seems to be the new "Thunderbird" series. Are they supported by the in-tree driver? (You may want to give the projects/head_mfi driver a try, by the way). Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJPUUe/AAoJEG80Jeu8UPuzarQH/ikAXsfhVrqDtN+jzxQTH+Fq g4FeXpxh1q5z7xiaURlt62ThvPJkrcXDnPepIPXkpcAr9MwJvmCPnhXRMt2Ond4s aD7C3pgcpYCfbRy7kusF0z/tdM4DevcL1o7yQa4qgv5EGIPfZonPHOvf5RDjIXTR 2wLhHsb1yvG6vJGwo/mmwlEZyiQIquLFWgD1Nxxcz78ZUkw6sAPccpbw7u/7k2W/ WUWa+3PksLmI7kH1vAGJ3fiEQWn9JKJy1WPSPk7ervKb/AwKAXr+0BeW4Z//LKP2 qk+Ir5CTCKl2Fv+RamRtGQJ/TQwT8Gt397pFItsdc3LZdQ3BT8bcKz07p2cn8Is= =3Gsx -----END PGP SIGNATURE----- From owner-freebsd-scsi@FreeBSD.ORG Fri Mar 2 23:19:33 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DD6E106564A for ; Fri, 2 Mar 2012 23:19:33 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id BD3828FC08 for ; Fri, 2 Mar 2012 23:19:32 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q22NJLDc096848 for ; Fri, 2 Mar 2012 15:19:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1330730361; bh=Pq67emg9hLcmAtwUNzqU7uRAI9vAo/whUCLxZ/XErRw=; h=Subject:From:Reply-To:To:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version; b=o1XXW/Res2iRsg2w3vJay37ajZSA5E7VVgSxP9xHZi+DY2ptrmSzdvb1J6/pWiSBo kwCcv6w2c86D1HYmerH6rpgLqHL9LgBnlkwbpjcV86NYerEKYMqF6cytm19dsf0AnA 8virjGxXRysk0M5Jm5p7jQlP4PDF+fXG20AndsGg= From: Sean Bruno To: "scsi@freebsd.org" In-Reply-To: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> References: <1330724697.5391.3.camel@powernoodle-l7.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-hrm7rJ6eC+gD80FAcOua" Date: Fri, 02 Mar 2012 15:19:20 -0800 Message-ID: <1330730360.5391.11.camel@powernoodle-l7.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: Subject: Re: [patch] Add New PCI ID to mfi(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "sbruno@freebsd.org" List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 23:19:33 -0000 --=-hrm7rJ6eC+gD80FAcOua Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2012-03-02 at 13:44 -0800, Sean Bruno wrote: > New megaraid SAS card from Dell coming down the pipe. I think this is > the right thing to do. Actually, after chatting with delphi, I'm holding off and letting him commit this via the head_mfi project branch. =20 Sean --=-hrm7rJ6eC+gD80FAcOua Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAABAgAGBQJPUVV4AAoJEL2UHwafTLtORv8H/iXzrRQPS6YLtyTzWCFiDX4d 13Vy7jSdNC7aJreoudsF4AXHdNAGfR8jR39fuBjz5fEmRabc4uvMoemXnjOGsalP Uw9PQTB85YpLKJCHGeVHdc/Epn/ZVbm+pdtMnrWCqGEp5+Qz6WIfmA9D44ISOzB9 p5M6YZrh3ko35JoJueOwNS2ch21dy13ZXyI4UBzJgsIZQjnX5SpXBe21FKqBqPXj vFP9ai1cz7hYh8QpQZfnX0zxVwwrTTXvmmQEph9pfG5L3GUmuvwafyXhkIUfjQGM 15GTio7ULrvlU2L9plc+IJgOXPzDX7gOPZCnNFUwbCxD3YMSPLQmyh8Vb7u7NcU= =inbK -----END PGP SIGNATURE----- --=-hrm7rJ6eC+gD80FAcOua-- From owner-freebsd-scsi@FreeBSD.ORG Sat Mar 3 11:10:31 2012 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 C5DE4106566C; Sat, 3 Mar 2012 11:10:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.c2i.net [212.247.155.2]) by mx1.freebsd.org (Postfix) with ESMTP id C6A9A8FC0C; Sat, 3 Mar 2012 11:10:30 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe09.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 72226834; Sat, 03 Mar 2012 12:10:28 +0100 From: Hans Petter Selasky To: freebsd-scsi@freebsd.org, Alexander Motin , gibbs@freebsd.org, freebsd-current@freebsd.org Date: Sat, 3 Mar 2012 12:08:48 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201203031208.48514.hselasky@c2i.net> Cc: Subject: CAM detach races with USB memory sticks 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: Sat, 03 Mar 2012 11:10:31 -0000 Hi, I've started looking into some attach/detach stress tests for USB mass storage devices. During my bughunting I've found the following issue: In /sys/cam/cam_xpt.c: 4569 void 4570 xpt_release_device(struct cam_ed *device) 4571 { 4572 4573 mjacob 224806 if (device->refcount == 1) { 4574 gibbs 39212 struct cam_devq *devq; 4575 4576 gibbs 44500 if (device->alloc_ccb_entry.pinfo.index != CAM_UNQUEUED_INDEX 4577 || device->send_ccb_entry.pinfo.index != CAM_UNQUEUED_INDEX) 4578 panic("Removing device while still queued for ccbs"); 4579 gibbs 49927 4580 if ((device->flags & CAM_DEV_REL_TIMEOUT_PENDING) != 0) XXXX HERE XXXX 4581 mjacob 224806 callout_stop(&device->callout); 4583 mav 198748 TAILQ_REMOVE(&device->target->ed_entries, device,links); 4584 device->target->generation++; 4585 device->target->bus->sim->max_ccbs -= device->ccbq.devq_openings; 4586 trasz 186184 /* Release our slot in the devq */ 4587 mav 198748 devq = device->target->bus->sim->devq; 4588 trasz 186184 cam_devq_resize(devq, devq->alloc_queue.array_size - 1); 4589 avatar 147571 camq_fini(&device->drvq); 4590 mav 198377 cam_ccbq_fini(&device->ccbq); 4591 ken 230590 /* 4592 * Free allocated memory. free(9) does nothing if the 4593 * supplied pointer is NULL, so it is safe to call without 4594 * checking. 4595 */ 4596 free(device->supported_vpds, M_CAMXPT); 4597 free(device->device_id, M_CAMXPT); 4598 free(device->physpath, M_CAMXPT); 4599 free(device->rcap_buf, M_CAMXPT); 4600 free(device->serial_num, M_CAMXPT); 4601 4602 mav 198748 xpt_release_target(device->target); 4603 avatar 147723 free(device, M_CAMXPT); Remember our OS is SMP now, so callout_drain() must be used on all callouts before the structure where they are located are freed. Above I only see callout_stop(). The problem is that xpt_release_device() appears to be called locked and callout_drain() requires unlocked context! How do we solve this? I don't know so much about the CAM layer and I hope that someone who does can give a hand here. --HPS