public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Bjorn Helgaas <bhelgaas@google.com>, <linux-rtc@vger.kernel.org>,
	<regressions@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION v6.1-rc1] rtc: cmos: rtcwake broken on NUC8i7HVK
Date: Tue, 18 Oct 2022 20:40:09 +0300	[thread overview]
Message-ID: <8735blm3nq.fsf@kernel.org> (raw)
In-Reply-To: <6b4aefb2-01a9-1489-8669-1af20e88f669@intel.com> (Rafael J. Wysocki's message of "Tue, 18 Oct 2022 18:36:36 +0200")

"Rafael J. Wysocki" <rafael.j.wysocki@intel.com> writes:

> On 10/18/2022 9:09 AM, Kalle Valo wrote:
>
>> Thorsten Leemhuis <regressions@leemhuis.info> writes:
>>
>>> On 17.10.22 18:58, Kalle Valo wrote:
>>>> I upgraded my NUC8i7HVK test box to v6.1-rc1 and noticed that my suspend
>>>> tests with ath11k were broken, the box never woke up from suspend
>>>> automatically and I had to manually push the power button to trigger
>>>> resume. This is the command I used:
>>>>
>>>> sudo rtcwake -m mem -s 30
>>>>
>>>> v6.0 works without problems and a bisect found this commit:
>>>>
>>>> commit 4919d3eb2ec0ee364f7e3cf2d99646c1b224fae8
>>>> Author:     Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>>> AuthorDate: Wed Oct 12 20:07:01 2022 +0200
>>>> Commit:     Alexandre Belloni <alexandre.belloni@bootlin.com>
>>>> CommitDate: Thu Oct 13 23:27:52 2022 +0200
>>>>
>>>>      rtc: cmos: Fix event handler registration ordering issue
>>> FWIW, Todd also reported this yesterday:
>>> https://lore.kernel.org/all/967cfe4e2dba242352ccd1cd00bdbcfb48bdd697.camel@linux.intel.com/
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216600
>>>
>>> And Zhang Rui provided a patch in bugzilla that should fix this.
>> Thanks, this is good info. Strangely enough Zhang's workaround in [1]
>> did not fix the issue for me, rtcwake is still broken. Unfortunately no
>> time right now to investigate further.
>>
>> [1] https://bugzilla.kernel.org/show_bug.cgi?id=216600#c3
>
> Please try https://lore.kernel.org/linux-acpi/5887691.lOV4Wx5bFT@kreacher/

This works, thanks!

Tested-by: Kalle Valo <kvalo@kernel.org>

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

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

      reply	other threads:[~2022-10-18 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87edv6mlow.fsf@kernel.org>
2022-10-18  6:33 ` [REGRESSION v6.1-rc1] rtc: cmos: rtcwake broken on NUC8i7HVK Thorsten Leemhuis
2022-10-18  7:09   ` Kalle Valo
2022-10-18 16:36     ` Rafael J. Wysocki
2022-10-18 17:40       ` Kalle Valo [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=8735blm3nq.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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