Re: [regression] suspend stress test stalls within 30 minutes

[Kalle Valo <kvalo@kernel.org>]

Pawan Gupta <pawan.kumar.gupta@linux.intel.com> writes:

> On Thu, May 16, 2024 at 12:03:22AM -0700, Pawan Gupta wrote:
>> I am running the suspend test now and will update in the morning if I
>> could reproduce the hang.
>
> Completed 500 suspend iterations, but the hang is not reproduced :(
> I have restarted the test.

In a way I'm not surprised as nobody else has reported anything similar.
I guess it's something really specific on my box, so weird.

> BTW, could you please share your /proc/cmdline?

This is the simplified command line with which I can reproduce the bug:

$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-6.9.0 root=UUID=61a268dc-df96-4e69-9272-928240dcc445 ro net.ifnames=0

> Also, was there any workload running with the suspend test?

There is no special workload when I reproduce the bug. This NUC box is
one of our test setups which I use to test ath11k and ath12k wireless
drivers, but when I'm debugging this suspend issue none of the wireless
drivers are not even loaded. I don't normally have a display connected
to the box but I do run netconsole, although I just verified that I see
the bug if I remove netconsole configuration from cmdline.

The distro is Ubuntu 20.04.6 LTS. Oh, but I do have installed a WCN6855
PCI module to the box so that I can test ath11k. That can of course make
a difference. And maybe also BIOS settings?

I think is easiest if I try get more info about with my box first, it
might be quite challenging for you to reproduce it.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches