From: Grzegorz Uriasz <gorbak25@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: artur@puzio.waw.pl, "Wei Liu" <wl@xen.org>,
jakub@bartmin.ski, "Andrew Cooper" <andrew.cooper3@citrix.com>,
marmarek@invisiblethingslab.com,
"Grzegorz Uriasz" <gorbak25@gmail.com>,
"Jan Beulich" <jbeulich@suse.com>,
j.nowak26@student.uw.edu.pl,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 0/1] Fix broken suspend on some machines
Date: Sun, 14 Jun 2020 14:36:27 +0000 [thread overview]
Message-ID: <cover.1592142369.git.gorbak25@gmail.com> (raw)
Hi,
The included patch is a small subset of a bigger patch set spanning few
projects aiming to isolate the GPU in Qubes OS to a dedicated security domain.
I'm doing this together with 3 colleagues as part of our Bachelors thesis.
While working on the project we came across 2 machines - newer gaming
laptops on which the suspend functionality on unmodified xen is completely broken.
The affected machines were able to suspend but not always resume. Even
if the resume succeeded then the kernel time was trashed in the dmesg log
and the machine never managed to suspend another time. After changing
the xen clock to hpet, suspend started working again both on stock
xen and Qubes OS - this indicates a bug in the ACPI PM Timer. After
disassembling the FADT ACPI table on the ASUS FX504GM I understood that the
reported bit width is 32 bits but the flags indicate a 24 bit PM timer.
The included patch fixes the suspend feature on ASUS FX504GM and hopefully
other laptops - Probably next week I will test this patch on my
friend's laptop where this issue also occurs(suspend is broken, trashed kernel
time after resume).
Grzegorz Uriasz (1):
x86/acpi: Use FADT flags to determine the PMTMR width
xen/arch/x86/acpi/boot.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.27.0
next reply other threads:[~2020-06-14 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 14:36 Grzegorz Uriasz [this message]
2020-06-14 14:36 ` [PATCH 1/1] x86/acpi: Use FADT flags to determine the PMTMR width Grzegorz Uriasz
2020-06-15 7:05 ` Roger Pau Monné
2020-06-16 8:07 ` Jan Beulich
2020-06-16 10:32 ` Roger Pau Monné
2020-06-16 12:31 ` Jan Beulich
2020-06-16 13:25 ` Jan Beulich
2020-06-16 14:59 ` Roger Pau Monné
2020-06-16 15:10 ` Grzegorz Uriasz
2020-06-16 15:13 ` Jan Beulich
2020-06-16 15:11 ` Jan Beulich
2020-06-16 15:25 ` Roger Pau Monné
2020-06-17 6:16 ` Grzegorz Uriasz
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=cover.1592142369.git.gorbak25@gmail.com \
--to=gorbak25@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=artur@puzio.waw.pl \
--cc=j.nowak26@student.uw.edu.pl \
--cc=jakub@bartmin.ski \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).