From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Wittlin-Cohen <jwittlincohen@gmail.com>
Cc: regressions@lists.linux.dev, stable@vger.kernel.org,
linux-scsi@vger.kernel.org, alim.akhtar@samsung.com,
bvanassche@acm.org, Kiwoong Kim <kwmad.kim@samsung.com>
Subject: Re: [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269)
Date: Thu, 15 Sep 2022 09:25:18 +0200 [thread overview]
Message-ID: <YyLTXk4RlTcFgCQY@kroah.com> (raw)
In-Reply-To: <CADy0EvLGJmZe-x9wzWSB6+tDKNuLHd8Km3J5MiWWYQRR2ctS3A@mail.gmail.com>
On Wed, Sep 14, 2022 at 10:21:04PM -0400, Jason Wittlin-Cohen wrote:
> #regzbot introduced 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269
>
> Issue: When running a 5.10.140 kernel compiled from kernel.org source, or a
> bisected kernel with commit 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269, 6 of
> the 48 drives attached to my LSI 9207-8e SAS HBA (P20 firmware, IT mode)
> will drop from the controller shortly after the boot process completes. At
> this point, the drives are not visible to the LSI controller, verified
> using LSI's lsiutil.x86_64 to list all attached devices, nor are the drives
> enumerated in /dev/disk/by-id. Attempts to access the drives result in I/O
> errors reported in syslog. At some point thereafter, the drives reappear
> and are accessible.
>
> Running a vanilla 5.10.139 kernel or a bisected kernel with commit
> 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269 removed, all 48 drives appear
> correctly, are listed in LSI's lsiutil tool, and appear in /dev/disk/by-id.
> No I/O errors are reported from any drive and none of the drives drop off
> the controller as experienced in 5.10.140. SMART testing shows normal
> results for all impacted drives.
Does this also have problems in the latest 5.15 and 5.19 release, or is
it somehow limited to 5.10.y?
Also, html emails are rejected by the mailing lists, so you might want
to resend it all in text-only mode so that everyone can see the full
details.
thanks,
greg k-h
prev parent reply other threads:[~2022-09-15 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADy0EvLGJmZe-x9wzWSB6+tDKNuLHd8Km3J5MiWWYQRR2ctS3A@mail.gmail.com>
2022-09-15 2:48 ` [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) Bart Van Assche
2022-09-22 11:38 ` Thorsten Leemhuis
2022-10-26 12:20 ` [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) #forregzbot Thorsten Leemhuis
2022-09-15 7:25 ` Greg KH [this message]
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=YyLTXk4RlTcFgCQY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alim.akhtar@samsung.com \
--cc=bvanassche@acm.org \
--cc=jwittlincohen@gmail.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).