From: Kai Liu <kai.liu@suse.com>
To: Chandrakanth Patil <chandrakanth.patil@broadcom.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 12:38:46 +0800 [thread overview]
Message-ID: <20200605043846.f3ciid3xpvdgumh6@suse.com> (raw)
In-Reply-To: <4285a7ff366d7f5cfb5cae582dadf878@mail.gmail.com>
On 2020/06/05 Fri 01:05, Chandrakanth Patil wrote:
>
>Hi Kai Liu,
>
>Gen3 (Invader) and Gen3.5 (Ventura/Aero) generations of controllers are
>affected.
Hi Chandrakanth,
My card is not one of these but it's also problematic:
# lspci -nn|grep 3408
02:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID Tri-Mode SAS3408 [1000:0017] (rev 01)
According to megaraid_sas.h it's Tomcat:
#define PCI_DEVICE_ID_LSI_TOMCAT 0x0017
According to product information on broadcom.com the card model is
9440-8i. So I tried to upgrade to the latest firmware version
51.13.0-3223 but I got these error:
# ./storcli64 /c0 download file=9440-8i_nopad.rom
Download Completed.
Flashing image to adapter...
CLI Version = 007.1316.0000.0000 Mar 12, 2020
Operating system = Linux 5.3.18-0.g6748ac9-default
Controller = 0
Status = Failure
Description = image corrupted
I tried few more versions from broadcom website, they all failed with
the same "image corrupted" error.
Here is the controller information:
# ./storcli64 /c0 show
Generating detailed summary of the adapter, it may take a while to complete.
CLI Version = 007.1316.0000.0000 Mar 12, 2020
Operating system = Linux 5.3.18-0.g6748ac9-default
Controller = 0
Status = Success
Description = None
Product Name = SAS3408
Serial Number = 033FAT10K8000236
SAS Address = 57c1cf15516f4000
PCI Address = 00:02:00:00
System Time = 06/05/2020 12:36:59
Mfg. Date = 00/00/00
Controller Time = 06/05/2020 04:36:58
FW Package Build = 50.6.3-0109
BIOS Version = 7.06.02.2_0x07060502
FW Version = 5.060.01-2262
Driver Name = megaraid_sas
Driver Version = 07.713.01.00-rc1
Vendor Id = 0x1000
Device Id = 0x17
SubVendor Id = 0x19E5
SubDevice Id = 0xD213
Host Interface = PCI-E
Device Interface = SAS-12G
Bus Number = 2
Device Number = 0
Function Number = 0
Domain ID = 0
Drive Groups = 3
Thanks,
Kai Liu
next prev parent reply other threads:[~2020-06-05 4:39 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
2020-06-05 4:38 ` Kai Liu [this message]
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=20200605043846.f3ciid3xpvdgumh6@suse.com \
--to=kai.liu@suse.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=jejb@linux.ibm.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).