From owner-freebsd-scsi@freebsd.org Mon Sep 26 08:53:48 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E95D6BEAB32 for ; Mon, 26 Sep 2016 08:53:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8F21ADC for ; Mon, 26 Sep 2016 08:53:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8Q8rmqY000116 for ; Mon, 26 Sep 2016 08:53:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Mon, 26 Sep 2016 08:53:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: prateekrootkey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 08:53:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #5 from prateek sethi --- Created attachment 175173 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175173&action= =3Dedit Adding some delay in the previous fix. Added a delay of 1 millisecond before retry for next time in case of mps_request_sync failure. I have tested this delay thing by changing return value of mps_request_syn= c to failure so get go into the retry path. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Mon Sep 26 09:02:20 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11F77BEAFCC for ; Mon, 26 Sep 2016 09:02:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01CD3FC9 for ; Mon, 26 Sep 2016 09:02:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8Q92J7P049369 for ; Mon, 26 Sep 2016 09:02:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Mon, 26 Sep 2016 09:02:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: prateekrootkey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 09:02:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #6 from prateek sethi --- (In reply to Sean Bruno from comment #3) Hi Sean, I have put an DELAY of 1 millisecond in the loop. I am not very sure about = the delay timing. Can you tell that 1 ms is fine or not? (In reply to Ngie Cooper from comment #4) Hi Ngie, Yes it can be a HBA firmware issue but I think it is good only if we have f= ix for those situations also.(In reply to Sean Bruno from comment #3) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Mon Sep 26 14:33:46 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 616A5BE9834 for ; Mon, 26 Sep 2016 14:33:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 51286E96 for ; Mon, 26 Sep 2016 14:33:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8QEXk3e031812 for ; Mon, 26 Sep 2016 14:33:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Mon, 26 Sep 2016 14:33:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 14:33:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #7 from Sean Bruno --- (In reply to prateek sethi from comment #6) Yeah, this looks like it will work. I don't have a problem with an error handler here. I'll wait a day or two for "strong objections" if there are = any. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Mon Sep 26 20:25:38 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABFF5BEA4F9 for ; Mon, 26 Sep 2016 20:25:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BD517FE for ; Mon, 26 Sep 2016 20:25:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8QKPcml022819 for ; Mon, 26 Sep 2016 20:25:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Mon, 26 Sep 2016 20:25:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slm@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 20:25:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 Stephen McConnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slm@freebsd.org --- Comment #8 from Stephen McConnell --- Hi Prateek, I'm not sure this is really the right thing to do to fix this because it just seems that we might be covering up a larger problem where t= he driver is doing something wrong. Can you attach the message file that shows= all of the output from the driver prior to the panic? I can take a look and see= if it gives me a clue as to what's going on. There are certain timing restrict= ions that need to be followed when resetting the controller - maybe those restrictions aren't being followed. Some cards are more sensitive to these restrictions than others and, if I remember correctly, the 2308 is one of t= hem. In any case, I think we should dig a little deeper first before committing = this change. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Mon Sep 26 20:52:10 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B2CCBEB128 for ; Mon, 26 Sep 2016 20:52:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B29ABAC for ; Mon, 26 Sep 2016 20:52:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8QKq90d082061 for ; Mon, 26 Sep 2016 20:52:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Mon, 26 Sep 2016 20:52:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slm@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 20:52:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #9 from Stephen McConnell --- Also, it might help to have the debug_level set to 0x07 before your test. If that's too much, and you can't reproduce, then you can try 0x05, and if tha= t's too much then the default of 0x04 will have to do. Looking at the code agai= n, the reset timing is probably OK, but I'd still like to see exactly where th= is is failing. Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Sep 27 09:19:52 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2F3ABEB769 for ; Tue, 27 Sep 2016 09:19:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2C0186E for ; Tue, 27 Sep 2016 09:19:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8R9JqLA036056 for ; Tue, 27 Sep 2016 09:19:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Tue, 27 Sep 2016 09:19:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: prateekrootkey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2016 09:19:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #10 from prateek sethi --- (In reply to Stephen McConnell from comment #9) Hi Stephen, I could not reproduce this issue now. system got panic after the mps reinit= got triggered. The following are the only logs I could find (before and after t= he crash).=20 Apr 27 13:34:51 Node1 kernel: mps0: Reinitializing controller Apr 27 14:52:21 Node1 syslogd: kernel boot file is /boot/kernel/kernel Apr 27 14:52:21 Node1 savecore: reboot after panic: mps_iocfacts_allocate failed to get IOC Facts with error 6 I got the message "mps0: Doorbell failed to activate" from the core analysi= s, which will help to find exact point of the issue. Hope these will be helpful for the further debugging.=20 Would you please mind throwing some light on the timing restrictions, that = you mentioned, to be followed when resetting the controller? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Tue Sep 27 19:18:29 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9C0DBEC16B for ; Tue, 27 Sep 2016 19:18:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A29099E0 for ; Tue, 27 Sep 2016 19:18:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8RJITr9077061 for ; Tue, 27 Sep 2016 19:18:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-scsi@FreeBSD.org Subject: [Bug 212841] getting panic during mps reinitialization. Date: Tue, 27 Sep 2016 19:18:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slm@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2016 19:18:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212841 --- Comment #11 from Stephen McConnell --- The reset timing in the driver looks fine to me. There is a requirement that the host wait a certain amount of time when it first accesses the controller during a reset, and then a certain time to wait on checking registers, etc. But, it looks fine. What doesn't make sense is that you're waiting some arbitrary amount of time after the initial failure and then it works. This time that your waiting is after the reset completes and then after some calls to other functions. Aft= er all of that, some access to the DOORBELL fails. Then, waiting 2 mSecs fixes= it. That's strange. There are two ways that this will fail in Step 4 of mps_request_sync(). The first is when reading the Interrupt Status REG. If this Register does not s= how an interrupt within 5 seconds, it fails (that's a really long time). The se= cond is when reading the DOORBELL REG. If the DOORBELL_USED bit is not set, it fails. I can't tell which one of these fails. But, because it fails your fix will just wait 2 mSecs and then retry, then it's successful (at least withi= n 10 mSecs - 5 retries). What I'm wondering is, does it really matter that you have a delay between mps_request_sync() calls? To me, it looks like something is messed up in FW= and just doing a retry fixes it. Now, with all of that said, I'm not sure there really is a better fix except that the delay may not need to be there. Having the delay there would make someone think that we're just not waiting long enough, which really is not = the case and looks a little scary, meaning someone could think the driver timing for this is very fragile, when it's really not. Sean, let me know what you think about removing the delay. If you want the delay, I would at least say to add a comment that explains the delay and re= try, since none of this is really supposed to happen and I think it's some FW or= HW workaround. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-scsi@freebsd.org Thu Sep 29 14:59:07 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3396EC019F0 for ; Thu, 29 Sep 2016 14:59:07 +0000 (UTC) (envelope-from Christophe.Aubry@keysource.be) Received: from mx01.keysource.be (webpub01.keysource.be [193.105.15.33]) by mx1.freebsd.org (Postfix) with ESMTP id F349CF8A for ; Thu, 29 Sep 2016 14:59:06 +0000 (UTC) (envelope-from Christophe.Aubry@keysource.be) Received: from remote.keysource.be (66.217-78-194.adsl-static.isp.belgacom.be [194.78.217.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx01.keysource.be (Postfix) with ESMTPSA id C56EDF6AB4 for ; Thu, 29 Sep 2016 16:48:56 +0200 (CEST) Received: from KEY-DC-01.dom-keysource.local ([fe80::3443:573e:ea40:ef42]) by KEY-DC-01.dom-keysource.local ([fe80::3443:573e:ea40:ef42%14]) with mapi id 14.02.0342.003; Thu, 29 Sep 2016 16:48:43 +0200 From: Christophe Aubry To: "freebsd-scsi@freebsd.org" Subject: LSI SAS 3008 - One slot of a SAS expander is not working properly Thread-Topic: LSI SAS 3008 - One slot of a SAS expander is not working properly Thread-Index: AdIaXgMdVLISZpPoRFe0c50RTEGxsA== Date: Thu, 29 Sep 2016 14:48:42 +0000 Message-ID: <692314937ED17744B3331B98D78F11DA01A2785F3F@KEY-DC-01.dom-keysource.local> Accept-Language: en-US, fr-BE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.22.2.88] x-esetresult: clean, is OK x-esetid: 37303A29E7B731676C756B Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2016 14:59:07 -0000 SGkgYWxsLA0KDQpJ4oCZbSBmYWNpbmcgYSBzdHJhbmdlIHByb2JsZW0gd2l0aCBhIExTSSBTQVMg MzAwOCBIQkEgKExTSSA5MzAwLTRpQSkgbXkgc2V0dXAgd2FzIHJ1bm5pbmcgc2luY2Ugb25lIHdl ZWsgd2l0aG91dCBhbnkgcHJvYmxlbSB3aGVuIHN1ZGRlbmx5IG9uZSBTU0Qgd2FzIHJlbW92ZSBi eSB0aGUgT1Mgb3IgWkZTIGJlY2F1c2Ugb2YgYSByZWFkL3dyaXRlIHRpbWVvdXQgKG1heWJlIHRy aW1taW5nIHByb2JsZW0gPykgYnV0IGl04oCZcyBub3QgdGhlIHNvdXJjZSBvZiBteSBwcm9ibGVt IGp1c3QgcmlnaHQgbm93IGluZGVlZCB0aGUgU1NEIHNlZW1zIHdvcmtpbmcgZmluZSBpbiBhbm90 aGVyIHNsb3Qgb2YgdGhlIGV4cGFuZGVyIG9yIGluIGFub3RoZXIgY29tcHV0ZXIuDQpNeSBwcm9i bGVtIGlzIHRoYXQgc2xvdCBpcyBub3Qgd29ya2luZyBhbnltb3JlIHVuZGVyIEZyZWVCU0Qgd2l0 aCBhbnkgZGlzaywgZmlybXdhcmUgb3IgZHJpdmVyICBjb21iaW5hdGlvbi4gSSB0cmllZCB0byBy ZWluc3RhbGwgdGhlIE9TIGFuZCB1cGdyYWRlIHRoZSBkcml2ZXIgYW5kIGZpcm13YXJlIGJ1dCB0 aGUgcHJvYmxlbSBpcyBzdGlsbCB0aGVyZSBob3dldmVyIHRoYXQgc2xvdCB3b3JraW5nIG5vcm1h bGx5IGludG8gdGhlIEJJT1Mgb2YgdGhlIEhCQSBvciB1bmRlciBMaW51eC4NCkkgbWFkZSBzb21l IHNlYXJjaCBhbmQgSSBoZWFyZCBhYm91dCBhIHRvb2wgY2FsbGVkIGxzaXV0aWwgd2hpY2ggaXMg YWJsZSB0byBjaGFuZ2UgdGhlIG1hcHBpbmcgb2YgdGhlIGRldmljZXMgd2l0aGluIHRoZSBCSU9T IG9mIHRoZSBIQkEgYnV0IHRoZSBmZXcgdmVyc2lvbnMgdGhhdCBJIGZvdW5kIHdvcmsgb25seSB1 bmRlciBMaW51eCBhbmQgdGhleSBkbyBub3QgZGV0ZWN0IG15IEhCQS4NCkRpZCBzb21lb25lIGtu b3cgd2hlcmUgSSBjYW4gb2J0YWluIHRoYXQgdG9vbCA/DQoNCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX18NCg0KQ2hyaXN0b3BoZSBBdWJyeQ0KU3lzdGVtIEVuZ2luZWVy DQoNClJvdXRlIGRlcyBtYXJuacOocmVzLCAzDQoxMzgwIExhc25lDQpCRQ0KDQpUZWw6IDAwMzIy NjI2MTMzMw0KRmF4OiAwMDMyMjYyNjEzMzkNCk1haWw6IENocmlzdG9waGUuQXVicnlAa2V5c291 cmNlLmJlIC0gd3d3LmtleXNvdXJjZS5iZQ0KDQoNCg== From owner-freebsd-scsi@freebsd.org Fri Sep 30 01:06:54 2016 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF851C00F76 for ; Fri, 30 Sep 2016 01:06:54 +0000 (UTC) (envelope-from erica.meyer@acquitment.com) Received: from acquitment.com (acquitment.com [162.144.62.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CD96413D6 for ; Fri, 30 Sep 2016 01:06:54 +0000 (UTC) (envelope-from erica.meyer@acquitment.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=acquitment.com; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Uf8DeexVz08jGLlbID2gGV8SYmcj+L/TPhCbyRYRYLo=; b=bTcX3VwRAu1xGpVRLQ1MceH+/J WrfPjuFYqQHMAmDHNywGHTItlrmPQO17RUOtQHCkAkUrRy5236Mg3AMjoO98lZP7EMbGGkvKd1osw ZQtX8AoeHPLKVodTs4h6Ea6XNTV3RM4aRlaTq1LmEZCeJyaH+8kgvaI2al4r7M0TQrIKvUMbgQ6Ey bhbsqmuW9mX8PeXyX9Zz0vWzxA9vo+Mmq/ZDbTNTVs9VuM9yfIwPJ4QHSzFmiuSQBlZJhVFlY2iAP NcE2c/KAORRRP/kSGomAytAeA6KgIxy2gx8efxNsp1A4fYUNr9jY4KN5Dr3TMdspkumsGD5SKCRjB dv2Hwlzg==; Received: from [106.51.25.248] (port=6121 helo=md12PC) by 162-144-64-20.webhostbox.net with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1bpjdU-0002pG-VQ for freebsd-scsi@freebsd.org; Thu, 29 Sep 2016 22:17:01 +0000 From: "erica meyer" To: Subject: PC World Users Email list Date: Thu, 29 Sep 2016 17:13:10 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdIanoUyR0UY52j4SDyhMNmMUrBtNQ== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - 162-144-64-20.webhostbox.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - acquitment.com X-Get-Message-Sender-Via: 162-144-64-20.webhostbox.net: authenticated_id: erica.meyer@acquitment.com X-Authenticated-Sender: 162-144-64-20.webhostbox.net: erica.meyer@acquitment.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Sep 2016 01:06:55 -0000 Hi, Hope all is well. We are a digital marketing company who will help you get in touch with your clients. Thereby increasing your revenue in terms of sales. We do offer a host of services like data base acquisition, email campaigns, data appending etc. Would you be interested in acquiring PC World Users list? Our list Includes: Company, Contact Name (First, Middle and Last name), Website, Mailing Address, Job title, Phone, Fax, Revenue Size, SIC Code, and Opt-In emails. Let me know your thoughts so that I can have someone from the marketing and sales help you further. Regards, Erica Meyer Demand Generation Executive To Opt Out, please respond "Leave Out" in the Subject line.