All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Hans de Goede <hdegoede@redhat.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	scsi <linux-scsi@vger.kernel.org>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Hannes Reinecke <hare@suse.de>,
	gzhqyz@gmail.com, "James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH] scsi: sd: Revert "Rework asynchronous resume support"
Date: Sun, 21 Aug 2022 19:52:30 -0700	[thread overview]
Message-ID: <ecf878dc-905b-f714-4c44-6c90e81f8391@acm.org> (raw)
In-Reply-To: <CAMuHMdVDWrLs_KusG8vXA_1z8ORdPnpfxzNqw4jCG_G0D-fn+A@mail.gmail.com>

On 8/21/22 02:16, Geert Uytterhoeven wrote:
> It looks like there is a (different) regression in v6.1-rc1 related
> to s2idle and s2ram, which is not fixed by this patch.  In fact it
> also happens on boards where SATA is not used, it is just less likely
> to happen on the non-SATA boards.
> I still have to bisect it, which may take some time, as the issue is
> not 100% reproducible.

Hi Geert,

What kind of regression are you encountering? A crash, a hang or 
something else? Are any call traces available?

I posted another revert earlier today but that revert is for code paths 
not related to suspend/resume functionality. See also 
https://lore.kernel.org/linux-scsi/20220821220502.13685-1-bvanassche@acm.org/

Thanks,

Bart.

  reply	other threads:[~2022-08-22  2:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:26 [PATCH] scsi: sd: Revert "Rework asynchronous resume support" Bart Van Assche
2022-08-16 18:00 ` John Garry
2022-08-16 18:06   ` Bart Van Assche
2022-08-17  8:20     ` John Garry
2022-08-17 20:06 ` Vlastimil Babka
2022-08-22 20:53   ` Vlastimil Babka
2022-08-20 15:37 ` Hans de Goede
2022-08-21  9:16   ` Geert Uytterhoeven
2022-08-22  2:52     ` Bart Van Assche [this message]
2022-08-23  6:41       ` Geert Uytterhoeven
2022-08-23 18:10         ` Bart Van Assche
2022-08-26  7:54           ` Geert Uytterhoeven

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=ecf878dc-905b-f714-4c44-6c90e81f8391@acm.org \
    --to=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=geert@linux-m68k.org \
    --cc=gzhqyz@gmail.com \
    --cc=hare@suse.de \
    --cc=hdegoede@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.