Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751561AbdFGBvJ (ORCPT ); Tue, 6 Jun 2017 21:51:09 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:30504 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751453AbdFGBvI (ORCPT ); Tue, 6 Jun 2017 21:51:08 -0400 Subject: Re: [PATCH v2] x86/smpboot: Make logical package management more robust To: Max Vozeler , Thomas Gleixner Cc: LKML , x86@kernel.org, Peter Zijlstra , Borislav Petkov , "Charles (Chas) Williams" , "M. Vefa Bicakci" , Alok Kataria , xen-devel , =?UTF-8?Q?Juergen_Gro=c3=9f?= , =?UTF-8?Q?Thomas_Wei=c3=9fschuh?= References: <8aa33de4-db18-759b-d2cb-0e25d5ab9d88@oracle.com> <730d61ff-ff1e-df80-3446-7fceb25a6d63@oracle.com> <60e7a807-27fb-f666-270a-9512804deae8@oracle.com> <20170606133958.GA23069@chaos.hinterhof.net> From: Boris Ostrovsky Message-ID: <20c3f46a-3514-99cb-30c3-cec6e42211cf@oracle.com> Date: Tue, 6 Jun 2017 21:48:37 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170606133958.GA23069@chaos.hinterhof.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1287 Lines: 42 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