All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	"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: Tue, 23 Aug 2022 11:10:37 -0700	[thread overview]
Message-ID: <026ad7cc-5be9-e90b-8c95-0649caf68779@acm.org> (raw)
In-Reply-To: <CAMuHMdW0WzgQjR33hz9om7ahE5StbDCLozVnZzYAS1WEzStR0w@mail.gmail.com>

On 8/22/22 23:41, Geert Uytterhoeven wrote:
> A lock-up (magic sysrq does not work) during s2idle.
> I tried bisecting it yesterday, but failed.
> On v6.0-rc1 (and rc2) it happens ca. 25% of the time, but the closer
> I get to v5.19, the less likely it is to happen. Apparently 100
> successful s2idle cycles was not enough to declare a kernel good...
> 
>      Freezing ...
>      Filesystems sync: 0.001 seconds
>      Freezing user space processes ... (elapsed 0.001 seconds) done.
>      OOM killer disabled.
>      Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
>      sd 0:0:0:0: [sda] Synchronizing SCSI cache
>      sd 0:0:0:0: [sda] Stopping disk
> 
> ---> hangs here if it happens
> 
>      ravb e6800000.ethernet eth0: Link is Down
>      sd 0:0:0:0: [sda] Starting disk
>      Micrel KSZ9031 Gigabit PHY e6800000.ethernet-ffffffff:00: attached
> PHY driver (mii_bus:phy_addr=e6800000.ethernet-ffffffff:00, irq=186)
>      ata1: link resume succeeded after 1 retries
>      ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>      ata1.00: configured for UDMA/133
>      OOM killer enabled.
>      Restarting tasks ... done.
>      random: crng reseeded on system resumption
>      PM: suspend exit
>      ravb e6800000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off

Hi Geert,

I'm not sure that is enough information to find the root cause. How 
about enabling the tp_printk boot option and to enable tracing for 
suspend/resume operations, e.g. as follows?

cd /sys/kernel/tracing &&
echo 256 > /sys/kernel/tracing/buffer_size_kb &&
echo nop > current_tracer &&
echo > trace &&
echo 1 > events/power/device_pm_callback_start/enable &&
echo 1 > events/power/device_pm_callback_end/enable &&
echo 1 > events/power/suspend_resume/enable &&
echo 1 > tracing_on

Thanks,

Bart.

  reply	other threads:[~2022-08-23 19:25 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
2022-08-23  6:41       ` Geert Uytterhoeven
2022-08-23 18:10         ` Bart Van Assche [this message]
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=026ad7cc-5be9-e90b-8c95-0649caf68779@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.