From: Mike Galbraith <efault@gmx.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
lkml <linux-kernel@vger.kernel.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>,
John Garry <john.garry@huawei.com>,
ericspero@icloud.com, jason600.groome@gmail.com,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: regression bisect --> 88f1669019bd " scsi: sd: Rework asynchronous resume support"
Date: Mon, 22 Aug 2022 11:51:54 +0200 [thread overview]
Message-ID: <dbde377fbefdf77323e00c6aeeac251273a8a36c.camel@gmx.de> (raw)
In-Reply-To: <b64ae172-505a-fbbe-688c-d2d7a713f9a4@leemhuis.info>
On Mon, 2022-08-22 at 11:11 +0200, Thorsten Leemhuis wrote:
> 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:
>
> https://lore.kernel.org/all/20220816172638.538734-1-bvanassche@acm.org/
> https://lore.kernel.org/regressions/dd6844e7-f338-a4e9-2dad-0960e25b2ca1@redhat.com/
> https://lore.kernel.org/all/98592410-dd31-9081-86be-fda67d3b06d2@suse.cz/
>
> See also:
> https://lore.kernel.org/all/ecf878dc-905b-f714-4c44-6c90e81f8391@acm.org/
Yup, missed all that. Hohum, tosses bisection on the 'dead bugs' pile.
-Mike
prev parent reply other threads:[~2022-08-22 9:58 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
2022-08-22 9:51 ` Mike Galbraith [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=dbde377fbefdf77323e00c6aeeac251273a8a36c.camel@gmx.de \
--to=efault@gmx.de \
--cc=bvanassche@acm.org \
--cc=ericspero@icloud.com \
--cc=hare@suse.de \
--cc=jason600.groome@gmail.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).