From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Slow (higher scheduling latency?) system after S3 - regression 4.17 -> 4.19 ?
Date: Thu, 26 Mar 2026 14:05:13 +0100 [thread overview]
Message-ID: <acUvCYfOBRGydNGL@mail-itl> (raw)
In-Reply-To: <330c25da-1f7b-4af1-b14c-1c5e732ea441@suse.com>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Thu, Mar 26, 2026 at 09:21:16AM +0100, Jan Beulich wrote:
> On 25.03.2026 20:13, Marek Marczykowski-Górecki wrote:
> > In the "bad" case, I see this extra line:
> > (XEN) [ 6.902973] Platform timer appears to have unexpectedly wrapped 1 times.
> >
> > But in an earlier run of the same build it's not there.
>
> And in that earlier run, did the post-S3 delays also not occur?
Regardless of the above message, the "bad" build had the post-S3 delays.
--
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:[~2026-03-26 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 12:23 Slow (higher scheduling latency?) system after S3 - regression 4.17 -> 4.19 ? Marek Marczykowski-Górecki
2026-03-25 19:13 ` Marek Marczykowski-Górecki
2026-03-26 8:21 ` Jan Beulich
2026-03-26 13:05 ` Marek Marczykowski-Górecki [this message]
2026-03-26 8:27 ` Jan Beulich
2026-03-26 12:44 ` Marek Marczykowski-Górecki
2026-03-26 13:20 ` Jan Beulich
2026-03-26 15:53 ` Marek Marczykowski-Górecki
2026-03-26 16:02 ` Jan Beulich
2026-03-27 12:47 ` Marek Marczykowski-Górecki
2026-04-02 8:23 ` Jan Beulich
2026-04-02 8:50 ` Jürgen Groß
2026-04-02 13:02 ` Marek Marczykowski-Górecki
2026-04-02 13:03 ` Jan Beulich
2026-04-03 13:55 ` Marek Marczykowski-Górecki
2026-04-06 15:29 ` Marek Marczykowski-Górecki
2026-04-07 6:14 ` Jan Beulich
2026-04-07 12:01 ` Marek Marczykowski-Górecki
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=acUvCYfOBRGydNGL@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=jbeulich@suse.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.