[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a5kofi96.fsf@kernel.org>
Date: Fri, 17 May 2024 20:41:41 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
Cc: Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, "Rafael J. Wysocki"
<rafael@...nel.org>, x86@...nel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, regressions@...ts.linux.dev, Jeff Johnson
<quic_jjohnson@...cinc.com>, Daniel Sneddon
<daniel.sneddon@...ux.intel.com>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
Pawan Gupta <pawan.kumar.gupta@...ux.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
Powered by blists - more mailing lists