archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Mike Galbraith <>, lkml <>
Cc: Bart Van Assche <>,
	Ming Lei <>, Hannes Reinecke <>,
	John Garry <>,,,
	"" <>
Subject: Re: regression bisect --> 88f1669019bd " scsi: sd: Rework asynchronous resume support"
Date: Mon, 22 Aug 2022 11:11:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi, this is your Linux kernel regression tracker.

On 21.08.22 09:34, Mike Galbraith wrote:
> Greetings,
> My box claims this patch is a dud for it, symptom being hang during
> suspend _after_ a successful suspend/resume cycle. Revert at bisect
> starting point and now HEAD (15b3f48a4339) confirms box's assertion.
> [...]
> # first bad commit: [88f1669019bd62b3009a3cebf772fbaaa21b9f38] scsi: sd: Rework asynchronous resume support

FYI, in case you missed it: there are multiple reports that this patch
is causing problems. A revert and a partial reverts are discussed:

See also:

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.

P.P.S.: Just to be sure, add this report to the regression tracking, too:

#regzbot ^introduced: 88f1669019bd62b3009a3
#regzbot dup-of:
#regzbot monitor:

  parent reply	other threads:[~2022-08-22  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21  7:34 regression bisect --> 88f1669019bd " scsi: sd: Rework asynchronous resume support" Mike Galbraith
2022-08-22  5:07 ` Mike Galbraith
2022-08-22  9:11 ` Thorsten Leemhuis [this message]
2022-08-22  9:51   ` Mike Galbraith

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \

* 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).