From: Tomas Henzl <thenzl@redhat.com>
To: Mahesh Rajashekhara <Mahesh.Rajashekhara@pmcs.com>,
JBottomley@Parallels.com, linux-scsi@vger.kernel.org
Cc: aacraid@pmc-sierra.com, Harry.Yang@pmcs.com,
Achim.Leubner@pmcs.com, Rich.Bono@pmcs.com
Subject: Re: [PATCH 1/1] aacraid: kdump fix
Date: Mon, 13 Jan 2014 12:12:15 +0100 [thread overview]
Message-ID: <52D3CA0F.1030306@redhat.com> (raw)
In-Reply-To: <1389601230-4792-1-git-send-email-Mahesh.Rajashekhara@pmcs.com>
On 01/13/2014 09:20 AM, Mahesh Rajashekhara wrote:
> Thanks for your review comments, Tomas
>
> We have initialized var in this driver patch. This patch fixes kernel panic issue while booting into the kdump kernel.
>
> We have triggered crash and kdump vmcore was successful. No issues seen while booting into the OS.
>
> Signed-off-by: Mahesh Rajashekhara <Mahesh.Rajashekhara@pmcs.com>
Please add a 'V2' to the subject line next time, so the maintainer may notice that the version is different,
otherwise - looks good, thanks
Tomas
> ---
> drivers/scsi/aacraid/aacraid.h | 2 +-
> drivers/scsi/aacraid/rx.c | 7 ++++---
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/aacraid/aacraid.h b/drivers/scsi/aacraid/aacraid.h
> index 9323d05..eaaf870 100644
> --- a/drivers/scsi/aacraid/aacraid.h
> +++ b/drivers/scsi/aacraid/aacraid.h
> @@ -12,7 +12,7 @@
> *----------------------------------------------------------------------------*/
>
> #ifndef AAC_DRIVER_BUILD
> -# define AAC_DRIVER_BUILD 30200
> +# define AAC_DRIVER_BUILD 30300
> # define AAC_DRIVER_BRANCH "-ms"
> #endif
> #define MAXIMUM_NUM_CONTAINERS 32
> diff --git a/drivers/scsi/aacraid/rx.c b/drivers/scsi/aacraid/rx.c
> index dada38a..bb9917c 100644
> --- a/drivers/scsi/aacraid/rx.c
> +++ b/drivers/scsi/aacraid/rx.c
> @@ -480,7 +480,7 @@ static int aac_rx_ioremap(struct aac_dev * dev, u32 size)
>
> static int aac_rx_restart_adapter(struct aac_dev *dev, int bled)
> {
> - u32 var;
> + u32 var = 0;
>
> if (!(dev->supplement_adapter_info.SupportedOptions2 &
> AAC_OPTION_MU_RESET) || (bled >= 0) || (bled == -2)) {
> @@ -500,13 +500,14 @@ static int aac_rx_restart_adapter(struct aac_dev *dev, int bled)
> if (bled && (bled != -ETIMEDOUT))
> return -EINVAL;
> }
> - if (bled || (var == 0x3803000F)) { /* USE_OTHER_METHOD */
> + if (bled && (var == 0x3803000F)) { /* USE_OTHER_METHOD */
> rx_writel(dev, MUnit.reserved2, 3);
> msleep(5000); /* Delay 5 seconds */
> var = 0x00000001;
> }
> - if (var != 0x00000001)
> + if (bled && (var != 0x00000001))
> return -EINVAL;
> + ssleep(5);
> if (rx_readl(dev, MUnit.OMRx[0]) & KERNEL_PANIC)
> return -ENODEV;
> if (startup_timeout < 300)
next prev parent reply other threads:[~2014-01-13 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 8:20 [PATCH 1/1] aacraid: kdump fix Mahesh Rajashekhara
2014-01-13 11:12 ` Tomas Henzl [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-23 10:07 Mahesh Rajashekhara
2014-01-08 6:34 ` Mahesh Rajashekhara
2014-01-10 13:03 ` 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=52D3CA0F.1030306@redhat.com \
--to=thenzl@redhat.com \
--cc=Achim.Leubner@pmcs.com \
--cc=Harry.Yang@pmcs.com \
--cc=JBottomley@Parallels.com \
--cc=Mahesh.Rajashekhara@pmcs.com \
--cc=Rich.Bono@pmcs.com \
--cc=aacraid@pmc-sierra.com \
--cc=linux-scsi@vger.kernel.org \
/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).