From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "M. Vefa Bicakci" <m.v.b@runbox.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Charles (Chas) Williams" <ciwillia@brocade.com>
Subject: Re: [PREEMPT-RT] Oops in rapl_cpu_prepare()
Date: Wed, 2 Nov 2016 18:23:28 +0100 [thread overview]
Message-ID: <20161102172327.qam4ylpewmwnnmlx@linutronix.de> (raw)
In-Reply-To: <26425897-5229-d2c5-1e1b-a08442441f68@runbox.com>
On 2016-11-01 13:15:53 [+0300], M. Vefa Bicakci wrote:
> Hello Sebastian,
Hi,
> The patch fixes the kernel oops for me.
>
> I am using a custom 4.8.5-based kernel on Qubes OS R3.2, which is based
> on Xen 4.6.3. Apparently, Xen also has a similar bug/flaw/quirk regarding
> the allocation of package identifiers for the virtual CPUs.
>
> Prior to your patch, my Xen-based virtual machines would intermittently
> crash most of the time at boot-up with the backtrace reported by Charles.
> Due to this, I was under the impression that this is a subtle race
> condition.
how hard is it to get such a xen setup up and running?
Sebastian
next prev parent reply other threads:[~2016-11-02 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:27 Oops in rapl_cpu_prepare() Charles (Chas) Williams
2016-10-21 10:56 ` [PREEMPT-RT] " Sebastian Andrzej Siewior
2016-10-21 21:03 ` Charles (Chas) Williams
2016-10-25 12:22 ` Sebastian Andrzej Siewior
2016-10-25 12:42 ` Sebastian Andrzej Siewior
2016-10-27 19:00 ` Charles (Chas) Williams
2016-10-28 8:03 ` Sebastian Andrzej Siewior
2016-11-01 10:15 ` M. Vefa Bicakci
2016-11-02 17:23 ` Sebastian Andrzej Siewior [this message]
2016-11-03 18:21 ` M. Vefa Bicakci
2016-11-02 9:16 ` Charles (Chas) Williams
2016-11-02 9:58 ` Sebastian Andrzej Siewior
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=20161102172327.qam4ylpewmwnnmlx@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ciwillia@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.v.b@runbox.com \
/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