From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Sébastien Chaumat" <euidzero@gmail.com>,
xen-devel@lists.xenproject.org, "Jan Beulich" <jbeulich@suse.com>,
"Juergen Gross" <jgross@suse.com>
Subject: Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD
Date: Wed, 6 Mar 2024 22:31:28 +0100 [thread overview]
Message-ID: <ZejgsTDBmsnmKeiG@mail-itl> (raw)
In-Reply-To: <2a609713-3eec-438e-80af-c1dfcfe598c4@amd.com>
[-- Attachment #1: Type: text/plain, Size: 3171 bytes --]
On Wed, Mar 06, 2024 at 02:37:20PM -0600, Mario Limonciello wrote:
> On 3/6/2024 14:34, Sébastien Chaumat wrote:
> >
> >
> > Le mer. 6 mars 2024 à 19:51, Mario Limonciello
> > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>> a écrit :
> >
> > On 3/6/2024 12:49, Sébastien Chaumat wrote:
> > >
> > >
> > > Le mer. 6 mars 2024 à 19:08, Mario Limonciello
> > > <mario.limonciello@amd.com <mailto:mario.limonciello@amd.com>
> > <mailto:mario.limonciello@amd.com
> > <mailto:mario.limonciello@amd.com>>> a écrit :
> > >
> > > On 3/6/2024 12:05, Sébastien Chaumat wrote:
> > > >
> > > >
> > > > Le mer. 6 mars 2024 à 18:33, Mario Limonciello
> > > > <mario.limonciello@amd.com
> > > > Also; I'd be really interested to hear what happens with
> > > s2idle with
> > > > Xen
> > > > now (if it works).
> > > >
> > > >
> > > > suspend to RAM now works :)
> > >
> > > Do you see /sys/power/suspend_stats/last_hw_sleep increasing
> > with your
> > > suspend cycle?
> > >
> > >
> > > No, it does not increase (0).
> > >
> >
> > OK, then in that case I suggest you run
> > https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py <https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py>
> > in the hypervisor to find out what's wrong.
> >
> >
> > It fails with xen (not bare metal) during the prerequisite tests :
> >
>
> The script might need some modifications for tests that don't make sense in
> the context of Xen.
>
> > ✅ GPIO driver `pinctrl_amd` available
> > Traceback (most recent call last):
> > File "/home/sch/Downloads/amd_s2idle.py", line 2447, in <module>
> > test = app.prerequisites()
> > ^^^^^^^^^^^^^^^^^^^
> > File "/home/sch/Downloads/amd_s2idle.py", line 1938, in prerequisites
> > if not check():
> > ^^^^^^^
> > File "/home/sch/Downloads/amd_s2idle.py", line 826, in check_msr
> > val = read_msr(reg, 0)
> > ^^^^^^^^^^^^^^^^
> > File "/home/sch/Downloads/amd_s2idle.py", line 813, in read_msr
> > val = struct.unpack("Q", os.read(f, 8))[0]
> > ^^^^^^^^^^^^^
> > OSError: [Errno 5] Input/output error
> >
> > Last line in the log is :
> > 2024-03-06 21:29:33,146 DEBUG: Lockdown: [none] integrity confidentiality
> >
>
> Do you have userspace MSR support compiled in? If not; that could explain
> that problem. But it's very unlikely you changed the MSRs.
> For the purpose of finding where the suspend problem is, I'd comment out
> that specific check for now.
The s2idle isn't supported in Xen yet. Only S3 is. In fact, I have some
work-in-progress patches for that, I may try testing them on this
system.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-06 21:31 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 9:56 [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD Sébastien Chaumat
2023-12-04 9:06 ` Jan Beulich
2023-12-04 19:17 ` Sébastien Chaumat
2023-12-05 8:17 ` Jan Beulich
2023-12-05 8:50 ` Sébastien Chaumat
2023-12-05 9:26 ` Sébastien Chaumat
2023-12-05 14:14 ` Sébastien Chaumat
2023-12-05 14:18 ` Jan Beulich
2023-12-05 16:19 ` Sébastien Chaumat
2023-12-05 20:31 ` Sébastien Chaumat
2023-12-06 7:15 ` Jan Beulich
2023-12-11 9:18 ` Sébastien Chaumat
2023-12-11 11:09 ` Sébastien Chaumat
2023-12-11 11:27 ` Jan Beulich
2023-12-11 14:17 ` Sébastien Chaumat
2023-12-11 14:21 ` Sébastien Chaumat
2023-12-18 16:21 ` Sébastien Chaumat
2023-12-18 16:44 ` Jan Beulich
2023-12-18 17:04 ` Sébastien Chaumat
2023-12-18 18:35 ` Sébastien Chaumat
2023-12-19 9:38 ` Jan Beulich
2023-12-19 13:15 ` Jan Beulich
2023-12-19 13:25 ` Jan Beulich
2023-12-19 15:15 ` Sébastien Chaumat
2023-12-19 19:03 ` Sébastien Chaumat
2023-12-19 23:06 ` Sébastien Chaumat
2023-12-19 23:11 ` Sébastien Chaumat
2023-12-19 23:50 ` Sébastien Chaumat
2023-12-20 0:23 ` Sébastien Chaumat
2023-12-20 10:06 ` Jan Beulich
2023-12-20 16:34 ` Sébastien Chaumat
2023-12-21 9:09 ` Jan Beulich
2023-12-21 12:40 ` Jan Beulich
2023-12-21 13:29 ` Juergen Gross
2023-12-21 15:22 ` Jan Beulich
2023-12-21 20:41 ` Sébastien Chaumat
2023-12-22 8:46 ` Jan Beulich
[not found] ` <CAKm-UmY126AfdGhWcZ3s9vwN9+ksVRRFEhOu0ZFMoDvxrqOibw@mail.gmail.com>
2023-12-22 14:38 ` Sébastien Chaumat
2023-12-27 10:20 ` Sébastien Chaumat
2023-12-27 11:43 ` Sébastien Chaumat
2024-01-02 20:23 ` Sébastien Chaumat
2024-01-16 15:52 ` Sébastien Chaumat
2024-01-16 16:18 ` Jan Beulich
2024-01-17 2:15 ` Mario Limonciello
2024-01-22 17:06 ` Sébastien Chaumat
2024-01-22 20:59 ` Mario Limonciello
2024-02-01 12:30 ` Sébastien Chaumat
2024-02-01 16:51 ` Sébastien Chaumat
2024-02-06 16:04 ` Sébastien Chaumat
2024-03-06 17:28 ` Sébastien Chaumat
2024-03-06 17:33 ` Mario Limonciello
2024-03-06 18:05 ` Sébastien Chaumat
2024-03-06 18:08 ` Mario Limonciello
2024-03-06 18:49 ` Sébastien Chaumat
2024-03-06 18:51 ` Mario Limonciello
2024-03-06 20:34 ` Sébastien Chaumat
2024-03-06 20:37 ` Mario Limonciello
2024-03-06 21:31 ` Marek Marczykowski-Górecki [this message]
2024-03-06 22:04 ` Mario Limonciello
2024-03-07 8:39 ` Jan Beulich
2024-03-08 9:55 ` Sébastien Chaumat
2024-10-10 14:45 ` David Woodhouse
2023-12-19 13:33 ` Jan Beulich
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=ZejgsTDBmsnmKeiG@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=euidzero@gmail.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=mario.limonciello@amd.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.