lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <470204a1-fe54-c4d8-5352-059334a65c1d@amd.com>
Date:   Tue, 22 Dec 2020 22:55:31 +0530
From:   Shyam Sundar S K <Shyam-sundar.S-k@....com>
To:     "Deucher, Alexander" <Alexander.Deucher@....com>,
        Alexander Monakov <amonakov@...ras.ru>
Cc:     "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        Hans de Goede <hdegoede@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: amd-pmc s2idle driver issues



On 12/22/2020 10:14 PM, Deucher, Alexander wrote:
> [AMD Public Use]
> 
>> -----Original Message-----
>> From: Alexander Monakov <amonakov@...ras.ru>
>> Sent: Tuesday, December 22, 2020 10:57 AM
>> To: Deucher, Alexander <Alexander.Deucher@....com>
>> Cc: platform-driver-x86@...r.kernel.org; S-k, Shyam-sundar <Shyam-
>> sundar.S-k@....com>; Hans de Goede <hdegoede@...hat.com>; linux-
>> kernel@...r.kernel.org
>> Subject: RE: amd-pmc s2idle driver issues
>>
>> On Tue, 22 Dec 2020, Deucher, Alexander wrote:
>>
>>>> Yes. Out-of-the-box it's a "modern standby" laptop. There's a "hidden"
>>>> bios menu with extra settings that apparently allows to select legacy S3.
>>>> I did not change it, so I'm testing the "modern" mode.
>>>>
>>>> Note that this driver fetches SMU version from MMIO, which looks odd
>>>> to
>>>> me:
>>>> elsewhere (i.e. in the amdgpu driver) SMU version is retrieved by
>>>> issuing the corresponding SMU command, as far as I can tell.
>>>
>>> There are multiple interfaces to the SMU. It's shared by the entire
>>> SoC on APUs.
>>
>> Just pointing that out because evidently this interface does not work on this
>> laptop, producing all-ones instead of something resembling a version
>> number.
>>
>> Which APU generations does this driver support? If it does not support
>> Renoir
>> (yet?) it should be documented in the Kconfig text. Is Renoir support related
>> to missing AMD0005 ACPI id binding, and borked version number info?
> 
> The current code supports both Raven/Picasso and Renoir parts. At least some Renoir parts are supported as that is what we are mainly testing now.  I'm not sure why some boards have AMDI0005 vs AMD0005. We'll have to check with the sbios or windows teams.
> 

I think newer sbios'es have the AMDI0005 for Renior also. So, I am guessing you might be running an older BIOS. This driver is supposed to work for all generations of RYZEN starting from Picasso (provided you the right bios which supports modern standby).

You can keep an eye if some of the devices are not entering the lowest device state if your kernel is built with this patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge&id=146f1ed852a87b802ed6e71c31e189c64871383c

Also, on my reference platform I see the debugfs giving some valid information. Since you have a sbios with AMD0005, I cannot comment much on it.

Thanks,
Shyam

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ