From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Xen crash after S3 suspend - Xen 4.13
Date: Wed, 18 Mar 2020 14:50:52 +0000 [thread overview]
Message-ID: <fa845540-fd8e-bc63-a3af-50673dede579@citrix.com> (raw)
In-Reply-To: <20200318141635.GW7869@mail-itl>
On 18/03/2020 14:16, Marek Marczykowski-Górecki wrote:
> Hi,
>
> In my test setup (inside KVM with nested virt enabled), I rather
> frequently get Xen crash on resume from S3. Full message below.
>
> This is Xen 4.13.0, with some patches, including "sched: fix resuming
> from S3 with smt=0".
>
> Contrary to the previous issue, this one does not happen always - I
> would say in about 40% cases on this setup, but very rarely on physical
> setup.
>
> This is _without_ core scheduling enabled, and also with smt=off.
>
> Do you think it would be any different on xen-unstable? I cat try, but
> it isn't trivial in this setup, so I'd ask first.
>
>
> (XEN) Xen BUG at sched_credit2.c:3474
> (XEN) ----[ Xen-4.13.0 x86_64 debug=n Not tainted ]----
Any chance you can reproduce with a debug build?
There is a good chance that an assertion might fire earlier than this BUG().
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-18 14:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:16 [Xen-devel] Xen crash after S3 suspend - Xen 4.13 Marek Marczykowski-Górecki
2020-03-18 14:50 ` Andrew Cooper [this message]
2020-03-18 22:10 ` Marek Marczykowski-Górecki
2020-03-19 0:28 ` Dario Faggioli
2020-03-19 0:59 ` Marek Marczykowski-Górecki
2020-03-23 0:09 ` Marek Marczykowski-Górecki
2020-03-23 8:14 ` Jan Beulich
2020-09-29 14:27 ` Marek Marczykowski-Górecki
2020-09-29 15:07 ` Jürgen Groß
2020-09-29 15:16 ` Marek Marczykowski-Górecki
2020-09-29 15:27 ` Jürgen Groß
2021-01-31 2:15 ` [Xen-devel] Xen crash after S3 suspend - Xen 4.13 and newer Marek Marczykowski-Górecki
2021-10-09 16:28 ` Marek Marczykowski-Górecki
2022-08-21 16:14 ` Marek Marczykowski-Górecki
2022-08-22 9:53 ` Jan Beulich
2022-08-22 10:00 ` Marek Marczykowski-Górecki
2022-09-20 10:22 ` Marek Marczykowski-Górecki
2022-09-20 14:30 ` Jan Beulich
2022-10-11 11:22 ` Marek Marczykowski-Górecki
2022-10-14 16:42 ` George Dunlap
2022-10-21 6:41 ` Juergen Gross
2022-08-22 15:34 ` Juergen Gross
2022-09-06 11:46 ` Juergen Gross
2022-09-06 12:35 ` Marek Marczykowski-Górecki
2022-09-07 12:21 ` Dario Faggioli
2022-09-07 15:07 ` marmarek
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=fa845540-fd8e-bc63-a3af-50673dede579@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.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 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).