From: Jan Beulich <jbeulich@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] xen-unstable (4.14 to be): Assertion '!preempt_count()' failed at preempt.c:36
Date: Wed, 4 Dec 2019 18:30:17 +0100 [thread overview]
Message-ID: <59ac3962-a947-337b-b758-7ecfb69561ca@suse.com> (raw)
In-Reply-To: <ce5bd41b-90ed-fcf3-9e2d-a536ff1fcf90@eikelenboom.it>
On 04.12.2019 18:21, Sander Eikelenboom wrote:
> On current xen-unstable (4.14 to be) and AMD cpu:
>
> After rebooting the host, while the guests are starting, I hit the assertion below.
> xen-staging-4.13 seems fine on the same machine.
Nothing between 4.13 RC4 and the tip of staging stands out,
so I wonder if you could bisect over this range? Or perhaps
someone else sees something I don't see (right now).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-04 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 17:21 [Xen-devel] xen-unstable (4.14 to be): Assertion '!preempt_count()' failed at preempt.c:36 Sander Eikelenboom
2019-12-04 17:30 ` Jan Beulich [this message]
2019-12-04 21:03 ` Sander Eikelenboom
2019-12-05 8:35 ` Durrant, Paul
2019-12-05 8:43 ` Jan Beulich
2019-12-05 8:47 ` Durrant, Paul
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=59ac3962-a947-337b-b758-7ecfb69561ca@suse.com \
--to=jbeulich@suse.com \
--cc=linux@eikelenboom.it \
--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).