All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 214311] megaraid_sas - no disks detected
Date: Sat, 11 Sep 2021 18:56:25 +0000	[thread overview]
Message-ID: <bug-214311-11613-UUZQP5rWtl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214311-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214311

--- Comment #2 from Salvatore Bonaccorso (carnil@debian.org) ---
Hi,

On Sat, Sep 04, 2021 at 11:23:59AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=214311
> 
>             Bug ID: 214311
>            Summary: megaraid_sas - no disks detected
>            Product: IO/Storage
>            Version: 2.5
>     Kernel Version: 5.10.0
>           Hardware: Intel
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: SCSI
>           Assignee: linux-scsi@vger.kernel.org
>           Reporter: jarek@poczta.srv.pl
>         Regression: No
> 
> Dell R340 with PERC H330 - disks not detected.
> 
> lspci:
> 
> 02:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 3008
> [Fury] (rev 02)
> 
> dmesg:
> 
> megaraid_sas 0000:02:00.0: Performance mode :Latency
> megaraid_sas 0000:02:00.0: FW supports sync cache: No
> megaraid_sas 0000:02:00.0: megasas_disable_intr_fusion is called
> outband_intr_mask:0x40000009
> megaraid_sas 0000:02:00.0: Ignore DCMD timeout: megasas_get_ctrl_info 5274
> megaraid_sas 0000:02:00.0: Could not get controller info. Fail from
> megasas_init_adapter_fusion 1865
> megaraid_sas 0000:02:00.0: Failed from megasas_init_fw 6406
> 
> This machine works OK with kernel 4.19.0. Debian 11, Clonezilla 2.7.3-19 does
> not detect disks.

This sounds very similar to one bug report which was reported
downstream in Debian at https://bugs.debian.org/992304

Followup to the bugzilla bug 214311
(https://bugzilla.kernel.org/show_bug.cgi?id=214311) suggests that it
works when booting with BIOS, not with UEFI boot.

Regards,
Salvatore

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2021-09-11 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 11:23 [Bug 214311] New: megaraid_sas - no disks detected bugzilla-daemon
2021-09-04 12:33 ` [Bug 214311] " bugzilla-daemon
2021-09-11 18:56 ` [Bug 214311] New: " Salvatore Bonaccorso
2021-09-11 18:56 ` bugzilla-daemon [this message]
2021-09-18  7:20 ` [Bug 214311] " bugzilla-daemon
2022-10-03  6:40 ` bugzilla-daemon
2022-10-04  8:41 ` bugzilla-daemon
2022-10-04 12:51 ` bugzilla-daemon
2022-10-28  9:12 ` bugzilla-daemon
2022-10-31 15:13 ` bugzilla-daemon
2023-12-11 14:11 ` bugzilla-daemon

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=bug-214311-11613-UUZQP5rWtl@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.