From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Max Vozeler <max@hinterhof.net>, Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, "Peter Zijlstra" <peterz@infradead.org>,
"Borislav Petkov" <bp@alien8.de>,
"Charles (Chas) Williams" <ciwillia@brocade.com>,
"M. Vefa Bicakci" <m.v.b@runbox.com>,
"Alok Kataria" <akataria@vmware.com>,
xen-devel <xen-devel@lists.xen.org>,
"Juergen Groß" <jgross@suse.com>,
"Thomas Weißschuh" <kernel@weissschuh.net>
Subject: Re: [PATCH v2] x86/smpboot: Make logical package management more robust
Date: Tue, 6 Jun 2017 21:48:37 -0400 [thread overview]
Message-ID: <20c3f46a-3514-99cb-30c3-cec6e42211cf@oracle.com> (raw)
In-Reply-To: <20170606133958.GA23069@chaos.hinterhof.net>
On 06/06/2017 09:39 AM, Max Vozeler wrote:
> Hi Thomas,
>
> there is a problem booting recent kernels on some Xen domUs hosted by
> provider JiffyBox.
>
> The kernel seems to crash just after logging
> [ 0.038700] SMP alternatives: switching to SMP code
Do you have the crash splat? Stack trace and such.
In fact, full boot log might be useful.
>
> We started seeing this with 4.9.2 and bisecting the 4.9 stable kernels
> determined that this commit introduced the problem. Reverting it from 4.9.2
> makes the kernel boot again.
>
> Older kernels (starting from 3.16 up to and including 4.9.1) were running
> fine in this setup. But recent mainline (tested 4.12-rc3) and 4.9.x both
> fail to boot there.
>
> Unfortunately we have no detailed information about the hypervisor or
> setup and the provider is not very forthcoming with details. I'm attaching
> dmesg of a successful boot (4.9.2 with this commit reverted).
>
> It shows a fairly old XEN version:
>
> [ 0.000000] Xen version: 3.1.2-416.el5 (preserve-AD)
This is a 10 year old hypervisor so it's not especially surprising that
newer kernels don't work. (If anything, I am surprised that you actually
booted 4.9 at all).
There have been a bunch of problems in this area (topology) on PV guests.
-boris
next prev parent reply other threads:[~2017-06-07 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 9:04 [PATCH] x86/smpboot: Make logical package management more robust Thomas Gleixner
2016-12-08 9:13 ` Borislav Petkov
2016-12-08 11:03 ` Peter Zijlstra
2016-12-08 12:49 ` Thomas Gleixner
2016-12-08 13:04 ` Peter Zijlstra
2016-12-08 13:09 ` Thomas Gleixner
2016-12-09 22:06 ` Thomas Gleixner
2016-12-09 23:02 ` Boris Ostrovsky
2016-12-09 23:00 ` Thomas Gleixner
2016-12-10 3:37 ` Boris Ostrovsky
2016-12-10 19:03 ` Thomas Gleixner
2016-12-10 3:27 ` Boris Ostrovsky
2016-12-10 19:09 ` Thomas Gleixner
2016-12-10 19:13 ` Thomas Gleixner
2016-12-11 3:23 ` Boris Ostrovsky
2016-12-12 10:04 ` [PATCH v2] " Thomas Gleixner
2016-12-12 19:07 ` Boris Ostrovsky
2016-12-13 11:16 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2017-06-06 13:39 ` [PATCH v2] " Max Vozeler
2017-06-07 1:48 ` Boris Ostrovsky [this message]
2017-06-07 12:19 ` Max Vozeler
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=20c3f46a-3514-99cb-30c3-cec6e42211cf@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=akataria@vmware.com \
--cc=bp@alien8.de \
--cc=ciwillia@brocade.com \
--cc=jgross@suse.com \
--cc=kernel@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.v.b@runbox.com \
--cc=max@hinterhof.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.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).