public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 219367] New: mpt3sas constant warnings and card resets on aarch64 Cortex-A72: _get_st_from_smid+0x54/0x70
Date: Wed, 09 Oct 2024 06:24:32 +0000	[thread overview]
Message-ID: <bug-219367-11613@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219367
           Summary: mpt3sas constant warnings and card resets on aarch64
                    Cortex-A72: _get_st_from_smid+0x54/0x70
           Product: SCSI Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Other
          Assignee: scsi_drivers-other@kernel-bugs.osdl.org
          Reporter: me@ndoo.sg
        Regression: No

After LSI 9300-8e is initialized, dmesg constantly outputs below error, and
card keeps timing out and resetting and re-probing drives, making it unusable.

WARNING: CPU: 3 PID: 0 at drivers/scsi/mpt3sas/mpt3sas_base.c:1532
_get_st_from_smid+0x54/0x70 [mpt3sas]

Observed on kernel versions:
6.10.0
6.10.11
6.10.12

Fedora 40 aarch64
Motherboard/SoC: SolidRun LX2160A CEx7 COM
Memory: 2x Micron 18ASF4G72HZ-3G2F1 (32GB each DDR4 3200MHz CL22 ECC SODIMM)

It may be an SoC/Cortex-A72 issue as there are several errata for memory/cache
issues on this ARM core.

However seeing as CA72 cores are relatively common in prosumer and hyperscale,
I'm seeking comment from mptXsas developers on whether any workaround is
possible.

Other notes: Am running OpenZFS that's in the midst of a resilver operation,
however the errors occasionally do appear even before the ZFS pool is imported.

Attached is the full bootlog and buffer.

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

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2024-10-09  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-219367-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox