On Fri, Apr 9, 2021 at 11:55 AM Frédéric Pierret <frederic.pierret@xxxxxxxxxxxx> wrote: > > Hi, > > Le 3/29/21 à 11:02 AM, Frédéric Pierret a écrit : > > Hi, > > First of all, thank you very much for your answer. > > > > Le 3/29/21 à 8:24 AM, Kashyap Desai a écrit : > >> Hi - > >> > >> Can you send us full dmesg logs of each working and non-working case. ? > > > > I've attached you the working case of one of the two motherboard, referenced here as ASUS, and the nonworking case on the third motherboard, referenced here as ASROCK. In both cases, I've attached you the full dmesg of the same LiveUSB a Fedora 33 with also the full dmesg when I do a rmmod and modprobe of megaraid_sas. > > > >> On 3rd motherboard was it any working combination of kernel, driver and FW ? > >> OR it never worked on 3rd mother board ? > > > > Unfortunately, no combination has worked on the ASROCK (third motherboard) (before or after firmware upgrade, multiple kernel versions (5.10.X and 5.11.Y), drivers) > > > >> Kashyap > >> > >>> -----Original Message----- > >>> From: Frédéric Pierret [mailto:frederic.pierret@xxxxxxxxxxxx] > >>> Sent: Sunday, March 28, 2021 10:26 PM > >>> To: kashyap.desai@xxxxxxxxxxxx; sumit.saxena@xxxxxxxxxxxx; > >>> shivasharan.srikanteshwara@xxxxxxxxxxxx; jejb@xxxxxxxxxxxxx; > >>> martin.petersen@xxxxxxxxxx > >>> Cc: megaraidlinux.pdl@xxxxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx > >>> Subject: MegaRaid SAS 9341-8i issue > >>> > >>> Hi, > >>> > >>> I'm having issue with a MegaRaid 9341-8i card which is properly working on > >>> two motherboards (kernel-5.10.25 and kernel-5.11.10) but not on a third > >>> for > >>> which I want it to work. I originally received this card with a firmware > >>> from > >>> 2018 and I've updated it to the latest from Broadcom website > >>> (24.21.0-0148) > >>> but in both cases, I've the same issue on the third motherboard: > >>> > >>> [ 14.013135] megaraid_sas 0000:01:00.0: BAR:0x1 BAR's > >>> base_addr(phys):0x00000000fe800000 mapped virt_addr:0x(ptrval) > >>> [ 14.013142] megaraid_sas 0000:01:00.0: FW now in Ready state > >>> [ 14.013148] megaraid_sas 0000:01:00.0: 63 bit DMA mask and 32 bit > >>> consistent mask > >>> [ 14.013933] megaraid_sas 0000:01:00.0: firmware supports msix : > >>> (96) > >>> [ 14.014439] megaraid_sas 0000:01:00.0: requested/available msix 5/5 > >>> [ 14.014445] megaraid_sas 0000:01:00.0: current msix/online cpus : > >>> (5/4) > >>> [ 14.014447] megaraid_sas 0000:01:00.0: RDPQ mode : (disabled) > >>> [ 14.014453] megaraid_sas 0000:01:00.0: Current firmware supports > >>> maximum commands: 272 LDIO threshold: 237 > >>> [ 14.014631] megaraid_sas 0000:01:00.0: Configured max firmware > >>> commands: 271 > >>> [ 14.015377] megaraid_sas 0000:01:00.0: Performance mode :Latency > >>> [ 14.015380] megaraid_sas 0000:01:00.0: FW supports sync cache : > >>> Yes > >>> [ 14.015388] megaraid_sas 0000:01:00.0: megasas_disable_intr_fusion is > >>> called outbound_intr_mask:0x40000009 > >>> [ 14.037098] megaraid_sas 0000:01:00.0: Init cmd return status FAILED > >>> for > >>> SCSI host 2 > >>> [ 14.037762] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6399 > >>> > >>> Trying to rmmod then modprobe leads to something that looks like stuck > >>> state or such: > >>> > >>> [ 570.269770] megaraid_sas 0000:01:00.0: BAR:0x1 BAR's > >>> base_addr(phys):0x00000000fe800000 mapped > >>> virt_addr:0x00000000f42ba0e1 [ 570.269775] megaraid_sas 0000:01:00.0: > >>> Waiting for FW to come to ready state [ 570.269780] megaraid_sas > >>> 0000:01:00.0: FW in FAULT state, Fault code:0x10000 subcode:0x0 > >>> func:megasas_transition_to_ready [ 570.269782] megaraid_sas > >>> 0000:01:00.0: System Register set: > >>> (***) > >>> [ 570.269908] megaraid_sas 0000:01:00.0: Failed to transition controller > >>> to > >>> ready from megasas_init_fw! > >>> [ 570.269919] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 639 > >>> > >>> The motherboard which is not working is a recent one: Asrock X570D4U-2L2T > >>> with a Ryzen 3900XT. > >>> > >>> I've read a lot of things on internet saying that might be CSM issues or > >>> such > >>> but no luck with that. On the two working motherboards, it works in > >>> legacy/UEFI only. I've also tested the card on a x16 or x8 slots, the same > >>> result. I've attempted to build megaraid driver provided from Broadcom > >>> (07.716.01.00-2). Up to a slight adjustment in a log call using older > >>> attribute > >>> "host_busy", I'm hitting an unrelated issue due to KBUILD_CFLAGS recursion > >>> in arch/x86/Makefile. > >>> > >>> After hours and hours of testing, I'm currently out of ideas. Does anyone > >>> has > >>> an idea or could help me into adding useful debug info in the driver or > >>> such? > >>> > >>> Thank very much in advance, > >>> Frédéric > > > > Best regards, > > Frédéric > > Is there something more I could provide and help into troubleshooting this issue? First time driver load fails due to IOC INIT failure(writeq API is used to fire IOC INIT to firmware). We have seen writeq does not work on a few platforms. Please try if below change fixes your issue: diff --git a/megaraid_sas_fusion.c b/megaraid_sas_fusion.c index 432a0bb..24ef592 100644 --- a/megaraid_sas_fusion.c +++ b/megaraid_sas_fusion.c @@ -291,7 +293,8 @@ static void megasas_write_64bit_req_desc(struct megasas_instance *instance, union MEGASAS_REQUEST_DESCRIPTOR_UNION *req_desc) { -#if defined(writeq) && defined(CONFIG_64BIT) +//#if defined(writeq) && defined(CONFIG_64BIT) +#if 0 u64 req_data = (((u64)le32_to_cpu(req_desc->u.high) << 32) | le32_to_cpu(req_desc->u.low)); writeq(req_data, &instance->reg_set->inbound_low_queue_port) Thanks, Sumit > > Best regards, > Frédéric >
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
