From: Askar Safin <safinaskar@gmail.com>
To: safinaskar@gmail.com
Cc: Dell.Client.Kernel@dell.com, andriy.shevchenko@linux.intel.com,
chetan.kumar@mediatek.com, chris.feng@mediatek.com,
hua.yang@mediatek.com, len.brown@intel.com,
liang.lu@mediatek.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, mario.limonciello@amd.com,
pavel@ucw.cz, rafael@kernel.org, regressions@lists.linux.dev,
stable@kernel.org, ting.wang@mediatek.com
Subject: Re: [REGRESSION][BISECTED] "Wakeup event detected during hibernation" on Dell Precision 7780 (was "[PATCH v4] PM: hibernate: Avoid missing wakeup events during hibernation")
Date: Sat, 25 Oct 2025 08:15:55 +0300 [thread overview]
Message-ID: <20251025051555.422427-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20251021125446.4384-1-safinaskar@gmail.com>
Askar Safin <safinaskar@gmail.com>:
> This is "dmesg --level=debug+" on v6.18-rc2-with-1796f808e4bb-reverted:
>
> https://zerobin.net/?0459f6411446622d#8i0Ifo6o68By3+UlYUr2t2KL7YLXsKEXrkfszpE77Rw=
This log contains WARNING. It is caused by unrelated bug, which is reproducible
both on real hardware and in Qemu. I reported it here:
https://lore.kernel.org/regressions/20251025050812.421905-1-safinaskar@gmail.com/
--
Askar Safin
prev parent reply other threads:[~2025-10-25 5:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 8:32 [PATCH v4] PM: hibernate: Avoid missing wakeup events during hibernation Chris Feng
2023-12-13 13:45 ` Rafael J. Wysocki
2025-10-21 12:54 ` [REGRESSION][BISECTED] "Wakeup event detected during hibernation" on Dell Precision 7780 (was "[PATCH v4] PM: hibernate: Avoid missing wakeup events during hibernation") Askar Safin
2025-10-21 14:29 ` Mario Limonciello
2025-12-09 6:02 ` Askar Safin
2025-12-10 3:42 ` Mario Limonciello
2025-12-25 23:01 ` Askar Safin
2025-10-25 5:15 ` 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=20251025051555.422427-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chetan.kumar@mediatek.com \
--cc=chris.feng@mediatek.com \
--cc=hua.yang@mediatek.com \
--cc=len.brown@intel.com \
--cc=liang.lu@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@kernel.org \
--cc=ting.wang@mediatek.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
all inboxes | Powered by JetHome®