From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: "Rafael Ávila de Espíndola" <rafael@espindo.la>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amdgpu: suspend-to-idle on a 4350G desktop
Date: Sun, 22 Jan 2023 20:31:43 -0600 [thread overview]
Message-ID: <982bd736-6b09-0ac4-e421-903f6a4baaf0@amd.com> (raw)
In-Reply-To: <87edrnu9mk.fsf@espindo.la>
On 1/21/2023 10:37, Rafael Ávila de Espíndola wrote:
> Hi,
>
> I have a desktop that doubles as a NAS, and would like to suspend it
> when not in use. It works, but when it comes back it is using about 7W
> more than before going to sleep.
>
> It looks like a6ed2035878e5ad2e43ed175d8812ac9399d6c40 is the
> culprit. The system doesn't even support S3:
>
> % cat /sys/power/mem_sleep
> [s2idle]
>
> And looks like the vendor decided that they should not define
> ACPI_FADT_LOW_POWER_S0. The MB is a Gigabyte B550I AORUS PRO AX with
> bios version F16e.
>
> Which systems had crashes when ACPI_FADT_LOW_POWER_S0 was not defined?
> Would it be possible to limit the check only to those systems or at
> least only to systems that have S3?
>
> I can build the amdgpu module without that check and see if the problem
> goes away if that would help.
>
> Thanks,
> Rafael
Rafael,
Can you please open a bug report here
https://gitlab.freedesktop.org/drm/amd/-/issues
And attach the log from:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py
Thanks,
next prev parent reply other threads:[~2023-01-23 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 16:37 amdgpu: suspend-to-idle on a 4350G desktop Rafael Ávila de Espíndola
2023-01-23 2:31 ` Limonciello, Mario [this message]
[not found] ` <MN0PR12MB6101F62407FB383609B2FB30E2CA9@MN0PR12MB6101.namprd12.prod.outlook.com>
2023-01-23 9:03 ` Rafael Ávila de Espíndola
2023-01-23 14:23 ` Rafael Ávila de Espíndola
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=982bd736-6b09-0ac4-e421-903f6a4baaf0@amd.com \
--to=mario.limonciello@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@espindo.la \
/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