All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jason Wittlin-Cohen <jwittlincohen@gmail.com>
Cc: stable@vger.kernel.org, linux-scsi@vger.kernel.org,
	alim.akhtar@samsung.com, Kiwoong Kim <kwmad.kim@samsung.com>,
	Bart Van Assche <bvanassche@acm.org>,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269)
Date: Thu, 22 Sep 2022 13:38:35 +0200	[thread overview]
Message-ID: <ddec1a2f-1d55-ac42-9877-0d7119d087cd@leemhuis.info> (raw)
In-Reply-To: <350ec615-ffe8-2e0e-149d-4bf45932a585@acm.org>

Hi, this is your Linux kernel regression tracker.

On 15.09.22 04:48, Bart Van Assche wrote:
> On 9/14/22 19:21, Jason Wittlin-Cohen wrote:
>> 8d5c106fe216bf16080d7070c37adf56a9227e60 is the first bad commit
>> commit 8d5c106fe216bf16080d7070c37adf56a9227e60
>> Author: Kiwoong Kim <kwmad.kim@samsung.com
>> <mailto:kwmad.kim@samsung.com>>
>> Date: Tue Aug 2 10:42:31 2022 +0900
>>
>> scsi: ufs: core: Enable link lost interrupt
>>
>> commit 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269 upstream.
>>
>> Link lost is treated as fatal error with commit c99b9b230149 ("scsi: ufs:
>> Treat link loss as fatal error"), but the event isn't registered as
>> interrupt source. Enable it.
> 
> Something must have gone wrong during the bisection process. Commit
> 8d5c106fe216 ("scsi: ufs: core: Enable link lost interrupt") only
> affects the UFS driver and hence cannot change the behavior of a SAS
> controller. How about repeating the bisection process?

Hmm, nothing happened here for a week. :-/ That's not how this should be
when it comes to regressions...

Jason, any news on this? A answer to Greg's question ("Does this also
have problems in the latest 5.15 and 5.19 release)") would be helpful.
Also: when your wrote "Running [...] a bisected kernel with commit
6d17a112e9a63ff6a5edffd1676b99e0ffbcd269 removed, [...]" I assume you
tested this with 5.10.y?

Side note: Sure, a bisection can easily got wrong, as Bart outlined. But
you also wrote "Running [...] a bisected kernel with commit
6d17a112e9a63ff6a5edffd1676b99e0ffbcd269 removed, [...]" sounds a lot
like the bisection didn't go sideways. Are you sure you nothing went
wrong when you tested this revert?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

#regzbot introduced 8d5c106fe216bf1608
#regzbot poke

  reply	other threads:[~2022-09-22 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  2:21 [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) Jason Wittlin-Cohen
2022-09-15  2:48 ` Bart Van Assche
2022-09-22 11:38   ` Thorsten Leemhuis [this message]
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 ` [REGRESSION] introduced in 5.10.140 causes drives to drop from LSI SAS controller (Bisected to 6d17a112e9a63ff6a5edffd1676b99e0ffbcd269) Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2022-09-15  2:13 Jason Wittlin-Cohen

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=ddec1a2f-1d55-ac42-9877-0d7119d087cd@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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 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.