From: Tomas Henzl <thenzl@redhat.com>
To: adam radford <aradford@gmail.com>
Cc: linux-scsi@vger.kernel.org, steve.masters@lsi.com,
michael.benz@lsi.com, bo.yang@lsi.com
Subject: Re: [PATCH 1/2] megaraid_sas: Remove the shutdown_controller call
Date: Mon, 05 Sep 2011 16:17:39 +0200 [thread overview]
Message-ID: <4E64DA03.4090409@redhat.com> (raw)
In-Reply-To: <CAHtARFE+pbaVgbEyxrdF6qyFgu4Km4QOi28wUzfVtc5_SRayAg@mail.gmail.com>
On 08/26/2011 02:00 AM, adam radford wrote:
> On Thu, Aug 25, 2011 at 1:17 AM, Tomas Henzl <thenzl@redhat.com> wrote:
>> In the meantime - I've sent two patches, what do you think about the second one?
>> It solves(hides) the problem too.
> Here are my thoughts on your patches:
>
> 1. You are not checking if (reset_devices) around these code changes
> to determine if you are in the kdump kernel, which is the only place
> you are seeing this issue.
> 2. You should only change behavior for the device ID's you are having
> issue with.
> 3. We need to update your PERC5 controller to the latest firmware,
> then try to reproduce.
This problem is fixed in firmware thanks to Adam (LSI), so neither patch is needed.
Tomas
>
> -Adam
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-05 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 15:35 [PATCH 0/2] megaraid_sas: Fix an errant command from hw Tomas Henzl
2011-08-24 15:35 ` [PATCH 1/2] megaraid_sas: Remove the shutdown_controller call Tomas Henzl
2011-08-24 20:55 ` adam radford
2011-08-25 8:17 ` Tomas Henzl
2011-08-26 0:00 ` adam radford
2011-09-05 14:17 ` Tomas Henzl [this message]
2011-08-24 15:35 ` [PATCH 2/2] megaraid_sas: Initialize the cmd field to a known value Tomas Henzl
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=4E64DA03.4090409@redhat.com \
--to=thenzl@redhat.com \
--cc=aradford@gmail.com \
--cc=bo.yang@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.benz@lsi.com \
--cc=steve.masters@lsi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).