linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chandrakanth Patil <chandrakanth.patil@broadcom.com>
To: Kai Liu <kai.liu@suse.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Kashyap Desai <kashyap.desai@broadcom.com>,
	Sumit Saxena <sumit.saxena@broadcom.com>,
	Xiaoming Gao <newtongao@tencent.com>,
	Shivasharan Srikanteshwara 
	<shivasharan.srikanteshwara@broadcom.com>,
	xiakaixu1987@gmail.com, jejb@linux.ibm.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH] scsi: megaraid_sas: fix kdump kernel boot hung caused by JBOD
Date: Fri, 5 Jun 2020 01:05:13 +0530	[thread overview]
Message-ID: <4285a7ff366d7f5cfb5cae582dadf878@mail.gmail.com> (raw)
In-Reply-To: <20200604155009.63mhbsoaoq6yra77@suse.com>

>Subject: Re: [PATCH] scsi: megaraid_sas: fix kdump kernel boot hung caused
>by JBOD
>
>On 2020/06/04 Thu 16:39, Chandrakanth Patil wrote:
>>
>>Hi Martin, Xiaoming Gao, Kai Liu,
>>
>>It is a known firmware issue and has been fixed. Please update to the
>>latest firmware available in the Broadcom support website.
>>Please let me know if you need any further information.
>
>Hi Chandrakanth,
>
>Could you let me know which megaraid based controllers are affected by this
>issue? All or
>some models or some generations?
>
>Best regards,
>Kai Liu

Hi Kai Liu,

Gen3 (Invader) and Gen3.5 (Ventura/Aero) generations of controllers are
affected.

Thanks,
Chandrakanth Patil

  reply	other threads:[~2020-06-04 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  7:31 [PATCH] scsi: megaraid_sas: fix kdump kernel boot hung caused by JBOD xiakaixu1987
2020-06-02 12:12 ` Kai Liu
2020-06-03  1:31 ` Martin K. Petersen
2020-06-03 13:34   ` Chandrakanth Patil
2020-06-04 11:09   ` Chandrakanth Patil
2020-06-04 15:50     ` Kai Liu
2020-06-04 19:35       ` Chandrakanth Patil [this message]
2020-06-05  4:38         ` Kai Liu
2020-06-05 15:30           ` Chandrakanth Patil
2020-06-06  4:50             ` Kai Liu

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=4285a7ff366d7f5cfb5cae582dadf878@mail.gmail.com \
    --to=chandrakanth.patil@broadcom.com \
    --cc=jejb@linux.ibm.com \
    --cc=kai.liu@suse.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=newtongao@tencent.com \
    --cc=shivasharan.srikanteshwara@broadcom.com \
    --cc=sumit.saxena@broadcom.com \
    --cc=xiakaixu1987@gmail.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).