Received-SPF: pass (google.com: domain of linux-kernel+bounces-182484-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Kalle Valo <kvalo@kernel.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Borislav Petkov <bp@alien8.de>,  Dave Hansen <dave.hansen@intel.com>,
  Thomas Gleixner <tglx@linutronix.de>,  Ingo Molnar <mingo@redhat.com>,
  Dave Hansen <dave.hansen@linux.intel.com>,  "Rafael J. Wysocki"
 <rafael@kernel.org>,  x86@kernel.org,  linux-pm@vger.kernel.org,
  linux-kernel@vger.kernel.org,  regressions@lists.linux.dev,  Jeff Johnson
 <quic_jjohnson@quicinc.com>,  Daniel Sneddon
 <daniel.sneddon@linux.intel.com>
Subject: Re: [regression] suspend stress test stalls within 30 minutes
References: <20240511184945.GDZj-9yaOEWqf1ng8u@fat_crate.local>
	<87h6f4jdrq.fsf@kernel.org> <878r0djxgc.fsf@kernel.org>
	<874jb0jzx5.fsf@kernel.org>
	<feaefaae-e25b-4a48-b6be-e20054f2c8df@intel.com>
	<20240515072231.z3wlyoblyc34ldmr@desk>
	<529C9374-DA6F-49C8-9B32-91741800F8E4@alien8.de>
	<20240515162747.6shmaoelc4mt7nro@desk> <878r0bhvjq.fsf@kernel.org>
	<20240516070315.swz2golcrfp3uvfd@desk>
	<20240516142513.qqy7wbmja5frizuj@desk>
Date: Fri, 17 May 2024 20:41:41 +0300
In-Reply-To: <20240516142513.qqy7wbmja5frizuj@desk> (Pawan Gupta's message of
	"Thu, 16 May 2024 07:25:13 -0700")
Message-ID: <87a5kofi96.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

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