linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerry Snitselaar <jsnitsel@redhat.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Sathya Prakash <sathya.prakash@broadcom.com>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: question about mpt3sas commit b424eaa1b51c
Date: Fri, 14 Apr 2023 15:56:08 -0700	[thread overview]
Message-ID: <mntv2b4lkp44gicraijquuyjqob3dhmxbmdyec7zmv6jgjihnd@t5vpa35dkeal> (raw)
In-Reply-To: <2e585944-b34f-5df0-54e3-fba1205c4c1f@leemhuis.info>

On Sun, Apr 09, 2023 at 10:59:32AM +0200, Linux regression tracking #adding (Thorsten Leemhuis) wrote:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
> 
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
> 
> On 08.04.23 21:18, Jerry Snitselaar wrote:
> > We've had some people trying to track a problem for months revolving
> > around a system hanging at shutdown, and last thing they see being a
> > message from mpt3sas about a reset. They quickly bisected down to the
> > commit below, and reverted it made the problem go away for the
> > customer.
> > 
> > b424eaa1b51c ("scsi: mpt3sas: Transition IOC to Ready state during shutdown")
> 
> FWIW, that should have been fae21608c31c ("scsi: mpt3sas: Transition IOC
> to Ready state during shutdown") (see reply-to-self from Jerry)
> 
> > I got asked to look at something since I recently at another issue
> > that involved mpt3sas at shutdown, so I was looking through the
> > history, saw this commit being mentined. Looking at it, I'm not sure
> > why it is doing what is doing.
> > [...]
> 
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
> 
> #regzbot ^introduced fae21608c31c
> #regzbot title scsi: mpt3sas: systems hang at shutdown
> #regzbot ignore-activity
> 
> This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify when
> the regression started to happen? Or point out I got the title or
> something else totally wrong? Then just reply and tell me -- ideally
> while also telling regzbot about it, as explained by the page listed in
> the footer of this mail.
> 
> Developers: When fixing the issue, remember to add 'Link:' tags pointing
> to the report (the parent of this mail). See page linked in footer for
> details.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.

#regzbot resolve: had them boot a kernel with mpt3sas disabled in the config, and they reproduced the hang.


  reply	other threads:[~2023-04-14 22:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 19:18 question about mpt3sas commit b424eaa1b51c Jerry Snitselaar
2023-04-08 20:59 ` question about mpt3sas commit fae21608c31c Jerry Snitselaar
2023-04-08 23:49   ` Jerry Snitselaar
2023-04-09  0:18   ` Jerry Snitselaar
2023-04-09  8:59 ` question about mpt3sas commit b424eaa1b51c Linux regression tracking #adding (Thorsten Leemhuis)
2023-04-14 22:56   ` Jerry Snitselaar [this message]
2023-04-11 13:09 ` Tomas Henzl
2023-04-11 15:43   ` Jerry Snitselaar
2023-04-19 13:46     ` Tomas Henzl

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=mntv2b4lkp44gicraijquuyjqob3dhmxbmdyec7zmv6jgjihnd@t5vpa35dkeal \
    --to=jsnitsel@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=regressions@lists.linux.dev \
    --cc=sathya.prakash@broadcom.com \
    --cc=sreekanth.reddy@broadcom.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).