From: Tom Rini <trini@ti.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-scsi@vger.kernel.org,
James Bottomley <JBottomley@parallels.com>,
Xiangliang Yu <yuxiangl@marvell.com>
Subject: Re: Commit a692b0e broke my mvsas card
Date: Mon, 16 Apr 2012 16:34:07 -0700 [thread overview]
Message-ID: <4F8CAC6F.6070907@ti.com> (raw)
In-Reply-To: <CABE8wwvbSsc02U_m+20-DQgsZ2gQCi_A6susCrmfyx_scQkccw@mail.gmail.com>
On 04/16/2012 04:12 PM, Dan Williams wrote:
> On Mon, Apr 16, 2012 at 3:42 PM, Tom Rini<trini@ti.com> 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
next prev parent reply other threads:[~2012-04-16 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 22:42 Commit a692b0e broke my mvsas card Tom Rini
2012-04-16 23:12 ` Dan Williams
2012-04-16 23:34 ` Tom Rini [this message]
2012-04-16 23:59 ` Dan Williams
2012-04-17 1:53 ` Tom Rini
2012-04-17 3:25 ` Dan Williams
2012-04-17 14:44 ` Tom Rini
2012-04-17 16:50 ` Dan Williams
2012-04-17 17:21 ` Tom Rini
2012-04-17 15:47 ` James Bottomley
2012-04-17 17:17 ` Dan Williams
2012-04-18 5:11 ` Dan Williams
2012-04-18 5:37 ` James Bottomley
2012-04-18 15:23 ` Tom Rini
2012-04-18 15:46 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8CAC6F.6070907@ti.com \
--to=trini@ti.com \
--cc=JBottomley@parallels.com \
--cc=dan.j.williams@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=yuxiangl@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.