X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU)
Date: Thu, 29 Sep 2022 21:14:38 +0000	[thread overview]
Message-ID: <bug-216516-215701-wMEykfqGhv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216516-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216516

--- Comment #25 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> So about 2.5 % of power (1.3398 Wh) was consumed.
> If the system was in perfect s2idle, this should have been less than 1% for
> 23 minutes.
> Bug 2.5 % pretty much matches about 700 seconds of "bad" s2idle after the
> initial 700 "good" s2idle seconds in deepest state

Yup so what we're seeing here is that basically after an event comes in from
the EC waking up the SOC, it never goes back to sleep properly.  I suspect
there is some underlying firmware issue leading to that behavior.

Can you please do the following:

1) add right after the usleep_range() you added before this:

amd_pmc_idlemask_read(pdev, pdev->dev, NULL);

2) Add
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=cb3e7d624c3ff34a300587929c82af7364cf5c09

That will get us some more debugging information at least when this happens.

> I guess that the deepest state has been interrupted by the remnant of what 
> completely wakes the system if i8042 and LNXSYBUS:00/PNP0C0D:00 are not
> disabled (see above).

I think you're right.  The underlying firmware issue is probably the same as
https://bugzilla.kernel.org/show_bug.cgi?id=215770

As a W/A can you have a try with acpi.ec_no_wakeup=1 on your kernel command
line?  That should stop EC from issuing any wakeups and triggering this other
firmware bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-09-29 21:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-216516-215701@https.bugzilla.kernel.org/>
2022-09-26 18:49 ` [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU) bugzilla-daemon
2022-09-27 13:15 ` bugzilla-daemon
2022-09-27 18:00 ` bugzilla-daemon
2022-09-27 18:05 ` bugzilla-daemon
2022-09-27 18:07 ` bugzilla-daemon
2022-09-28 15:55 ` bugzilla-daemon
2022-09-28 16:29 ` bugzilla-daemon
2022-09-28 16:36 ` bugzilla-daemon
2022-09-28 16:57 ` bugzilla-daemon
2022-09-28 17:06 ` bugzilla-daemon
2022-09-28 23:45 ` bugzilla-daemon
2022-09-29 21:14 ` bugzilla-daemon [this message]
2022-09-29 23:29 ` bugzilla-daemon
2022-09-29 23:52 ` bugzilla-daemon
2022-09-30  0:37 ` bugzilla-daemon
2022-09-30  1:01 ` bugzilla-daemon
2022-09-30 10:38 ` bugzilla-daemon
2022-09-30 12:32 ` bugzilla-daemon
2022-09-30 15:50 ` bugzilla-daemon
2022-10-03 17:21 ` bugzilla-daemon
2022-10-12 17:39 ` bugzilla-daemon
2022-10-12 17:53 ` bugzilla-daemon
2022-10-12 18:04 ` bugzilla-daemon
2022-10-13  1:17 ` bugzilla-daemon

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=bug-216516-215701-wMEykfqGhv@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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