From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Subject: Re: Commit a692b0e broke my mvsas card Date: Mon, 16 Apr 2012 16:34:07 -0700 Message-ID: <4F8CAC6F.6070907@ti.com> References: <20120416224250.GA1983@bill-the-cat> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:39046 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751734Ab2DPXe7 (ORCPT ); Mon, 16 Apr 2012 19:34:59 -0400 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Dan Williams Cc: linux-scsi@vger.kernel.org, James Bottomley , Xiangliang Yu On 04/16/2012 04:12 PM, Dan Williams wrote: > On Mon, Apr 16, 2012 at 3:42 PM, Tom Rini wrote: >> Hey all, >> >> I have an OCZ RevoDrive3 X2 (which the mvsas driver works for). I've >> been running mainline since support for my card was added and I just >> went to test 3.3-rc4. Unpatched I get some sort of recursive fault that > > I assume this was supposed to be 3.4-rc3? Yes, sorry. >> locks up the system. When I revert a692b0e (which I found with a git >> bisect) things are working as expected again. What info do you need >> from me to work out the right solution here? Thanks! > > Can you post the kernel log of the fault (starting at the first sign > of trouble)? > > I suspect it's one of the known regression fixes [1], but would like > to double check. I merged those changes in and the problem is now non-fatal but now I'm missing 2 of the 4 drives on the card. Portion of dmesg is at http://pastebin.com/36K7xwHK and I can email it if needed. -- Tom