Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753890AbdLMT6l (ORCPT ); Wed, 13 Dec 2017 14:58:41 -0500 Received: from mail-qt0-f182.google.com ([209.85.216.182]:36133 "EHLO mail-qt0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751644AbdLMT6h (ORCPT ); Wed, 13 Dec 2017 14:58:37 -0500 X-Google-Smtp-Source: ACJfBotGMBO546VmzNvGNXbwiXmRiUrnH12Kwxqulc1P0+MiAOUaZ+ztRelR+hkHqo79HElRPBFRRg== Date: Wed, 13 Dec 2017 11:58:33 -0800 From: Jakub Kicinski To: =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= Cc: LKML , "netdev@vger.kernel.org" Subject: Re: x86 boot broken on -rc1? Message-ID: <20171213115833.11e2d097@cakuba.netronome.com> In-Reply-To: References: <20171201163954.2e356787@cakuba.netronome.com> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id vBDJwikW021354 Content-Length: 494 Lines: 12 On Wed, 13 Dec 2017 20:37:02 +0100, Björn Töpel wrote: > 2017-12-02 1:39 GMT+01:00 Jakub Kicinski: > > [ 5.777076] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 > > Yes, I'm getting that as well (v4.15-rc2-772-gcdc0974f10cf). > > Did you bisect it? I haven't got around yet. Yup, it's fixed but I'm not sure who far it trickled down the various trees: 947134d9b00f ("x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation")