From: Askar Safin <safinaskar@gmail.com>
To: andriy.shevchenko@linux.intel.com
Cc: Dell.Client.Kernel@dell.com, bartosz.golaszewski@linaro.org,
benjamin.tissoires@redhat.com, dmitry.torokhov@gmail.com,
linux-acpi@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-i2c@vger.kernel.org, regressions@lists.linux.dev,
rrangel@chromium.org, safinaskar@zohomail.com,
superm1@kernel.org, wse@tuxedocomputers.com
Subject: Re: [REGRESSION][BISECTED] Dell Precision 7780 wakes up on its own from suspend
Date: Thu, 18 Sep 2025 21:33:36 +0300 [thread overview]
Message-ID: <20250918183336.5633-1-safinaskar@gmail.com> (raw)
In-Reply-To: <aKyDB7h7cUBOLbiJ@smile.fi.intel.com>
Andy Shevchenko:
> In other words we need to enable debug of the pin control subsystem and see
> what it will print in dmesg.
You mean I should enable CONFIG_DEBUG_PINCTRL? Okay, I did this.
So, today I tested everything on fresh kernel, 6.17.0-rc6, without any
patches.
My config is: https://zerobin.net/?ebecc538f6caa22b#88c2k08G8+cZoMjgU9N/WYy28qQjyBW+/H78ygujZxY=
It was generated from Debian config using localmodconfig.
I added few tweaks, in particular I enabled CONFIG_DEBUG_PINCTRL.
# cat /proc/cmdline
BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.17.0-rc6 root=UUID=015793d4-ad51-4da7-844b-fcc3bcb13a0b ro rootflags=subvol=@rootfs log_buf_len=4M ignore_loglevel
I run this script:
https://zerobin.net/?327f3aa3ef7ce845#Ycu017J9YbRga8uGaCKRzsH7J/lB8D4RudpwTll5lbo=
This script runs "rtcwake -s 6 -m mem" multiple times. Sometimes my laptop wakes on timer (because of rtcwake),
and sometimes it wakes up too early on its own (and this is a bug).
My script did suspend 7 times:
# dmesg | grep s2idle
[ 117.934504] PM: suspend entry (s2idle)
[ 127.141741] PM: suspend entry (s2idle)
[ 131.299554] PM: suspend entry (s2idle)
[ 140.034802] PM: suspend entry (s2idle)
[ 144.592260] PM: suspend entry (s2idle)
[ 154.038621] PM: suspend entry (s2idle)
[ 163.034299] PM: suspend entry (s2idle)
Out of them my laptop woke up on timer 4 times and on its own (i. e. due to bug) 3 times:
# dmesg | grep 'woke up'
[ 126.087936] will-wake: attempt 0: woke up in time
[ 130.248820] will-wake: attempt 1: woke up early
[ 138.988770] will-wake: attempt 2: woke up in time
[ 143.545973] will-wake: attempt 3: woke up early
[ 152.993654] will-wake: attempt 4: woke up in time
[ 161.988956] will-wake: attempt 5: woke up in time
[ 166.329080] will-wake: attempt 6: woke up early
Here is full output of "dmesg --level=debug+":
https://zerobin.net/?f704a2d56603f4ec#SRrzc2mt2FNNqcltx/ULmtLZRdRH9frdgoODU03AXwE=
/proc/interrupts:
https://zerobin.net/?b7ba5047ca84ab29#TjMUjkAdhpIuKbnvPpuYyNWa/ilA/ciGKwwSbx6KRFc=
# head -n 1000 /sys/class/dmi/id/*
==> /sys/class/dmi/id/bios_date <==
07/15/2025
==> /sys/class/dmi/id/bios_release <==
1.23
==> /sys/class/dmi/id/bios_vendor <==
Dell Inc.
==> /sys/class/dmi/id/bios_version <==
1.23.6
==> /sys/class/dmi/id/board_asset_tag <==
==> /sys/class/dmi/id/board_name <==
0C6JVW
==> /sys/class/dmi/id/board_serial <==
/JNLHW44/VNCMV0046P029A/
==> /sys/class/dmi/id/board_vendor <==
Dell Inc.
==> /sys/class/dmi/id/board_version <==
A00
==> /sys/class/dmi/id/chassis_asset_tag <==
==> /sys/class/dmi/id/chassis_serial <==
JNLHW44
==> /sys/class/dmi/id/chassis_type <==
10
==> /sys/class/dmi/id/chassis_vendor <==
Dell Inc.
==> /sys/class/dmi/id/chassis_version <==
==> /sys/class/dmi/id/ec_firmware_release <==
1.18
==> /sys/class/dmi/id/modalias <==
dmi:bvnDellInc.:bvr1.23.6:bd07/15/2025:br1.23:efr1.18:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0C6JVW:rvrA00:cvnDellInc.:ct10:cvr:sku0C42:
==> /sys/class/dmi/id/power <==
head: error reading '/sys/class/dmi/id/power': Is a directory
==> /sys/class/dmi/id/product_family <==
Precision
==> /sys/class/dmi/id/product_name <==
Precision 7780
==> /sys/class/dmi/id/product_serial <==
JNLHW44
==> /sys/class/dmi/id/product_sku <==
0C42
==> /sys/class/dmi/id/product_uuid <==
4c4c4544-004e-4c10-8048-cac04f573434
==> /sys/class/dmi/id/product_version <==
==> /sys/class/dmi/id/subsystem <==
head: error reading '/sys/class/dmi/id/subsystem': Is a directory
==> /sys/class/dmi/id/sys_vendor <==
Dell Inc.
==> /sys/class/dmi/id/uevent <==
MODALIAS=dmi:bvnDellInc.:bvr1.23.6:bd07/15/2025:br1.23:efr1.18:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0C6JVW:rvrA00:cvnDellInc.:ct10:cvr:sku0C42:
Output of dmidecode:
https://zerobin.net/?e7783ba3bd93c895#EAVgKSZQrn0aGC6t9a/RKeZpp1/9TAYlDhHMh2lcpfQ=
--
Askar Safin
prev parent reply other threads:[~2025-09-18 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 23:32 [REGRESSION][BISECTED] Dell Precision 7780 wakes up on its own from suspend Askar Safin
2025-06-27 0:35 ` Mario Limonciello
2025-06-27 3:51 ` Askar Safin
2025-06-27 3:58 ` Mario Limonciello
2025-06-30 7:14 ` Askar Safin
2025-06-30 18:40 ` Mario Limonciello
2025-07-17 23:29 ` Askar Safin
2025-07-18 15:13 ` Werner Sembach
2025-07-18 15:20 ` Mario Limonciello
2025-08-25 15:34 ` Andy Shevchenko
2025-08-25 15:36 ` Andy Shevchenko
2025-09-18 18:33 ` Askar Safin [this message]
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=20250918183336.5633-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rrangel@chromium.org \
--cc=safinaskar@zohomail.com \
--cc=superm1@kernel.org \
--cc=wse@tuxedocomputers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).