From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Mateusz Jończyk" <mat.jonczyk@o2.pl>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Carsten Hatger" <xmb8dsv4@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
x86@kernel.org
Subject: Fwd: Read from RTC broken upon resume from suspend on HP Pro x360 435 G9 w/ AMD Ryzen 7 5825U
Date: Mon, 3 Jul 2023 20:25:35 +0700 [thread overview]
Message-ID: <591e089a-6ccd-c5f3-4cd4-a332e2eae724@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Dear all,
>
> read access to the device's RTC fails upon resume from suspend with the following error message grabbed from the kernel ring buffer:
>
> [409610.163139] Unable to read current time from RTC
>
> The issue is rare and more likely to appear if the system has been in standby for more than 24hrs w/o interruption.
>
> Same issue is reported to appear on HP Elite G9 devices, cf. https://bbs.archlinux.org/viewtopic.php?id=283620
>
> The issue screws up the systems time resulting in erroneous dated log entries, failing authentication, ..., thus requiring a reboot.
>
> Please see attached dmesg output (line 2069) for further information.
>
> AMD staff member suspected commit d2a632a8a11756197deb1341bbb09c09abaf20ce to cause a race condition, thus being responsible for the issue. They suggested to increase the delays introduced by latter commmit to 300us. Unfortunately this does not resolve the issue.
>
> Any help would be appreciated.
See Bugzilla for the full thread and attached dmesg.
Mateusz: It looks like this regression is caused by a commit of yours.
Would you like to take a look on it?
Anyway, I'm adding it to regzbot:
#regzbot introduced: d2a632a8a11756 https://bugzilla.kernel.org/show_bug.cgi?id=217626
#regzbot title: reducing RTC_UIP polling period causes broken RTC on resume from suspend
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217626
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-07-03 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 13:25 Bagas Sanjaya [this message]
2023-09-29 14:06 ` Linux regression tracking #update (Thorsten Leemhuis)
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=591e089a-6ccd-c5f3-4cd4-a332e2eae724@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=regressions@lists.linux.dev \
--cc=x86@kernel.org \
--cc=xmb8dsv4@gmail.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®