Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750847AbdL2VRu (ORCPT ); Fri, 29 Dec 2017 16:17:50 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:33418 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750709AbdL2VRt (ORCPT ); Fri, 29 Dec 2017 16:17:49 -0500 X-Google-Smtp-Source: ACJfBos/XHfceFsa4xBqfC/XDdNL1Q7SZqW2ZiPo349pBN2jEm70or6V8c6c1dDXXS8/a7/8wTFPQaGCdl4KvQRQ1kA= MIME-Version: 1.0 In-Reply-To: <33249a35-7d6a-f0f3-5a98-e6474f9366e3@gmx.de> References: <33249a35-7d6a-f0f3-5a98-e6474f9366e3@gmx.de> From: Linus Torvalds Date: Fri, 29 Dec 2017 13:17:47 -0800 X-Google-Sender-Auth: sJrpfEfpharfnP2BaA28lFs2eBw Message-ID: Subject: Re: 4.14.9 doesn't boot (regression) To: =?UTF-8?Q?Toralf_F=C3=B6rster?= , Alexander Tsoy Cc: Andy Lutomirski , stable , Linux Kernel , "the arch/x86 maintainers" 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 mail.home.local id vBTLHtFJ019458 Content-Length: 1716 Lines: 51 On Fri, Dec 29, 2017 at 1:02 PM, Toralf Förster wrote: > On 12/29/2017 09:12 PM, Linus Torvalds wrote: >> instead, and see if that makes a difference, that would narrow down >> the possible root cause of this problem. > > not at this ThinkPad T440s (didn't test at the server with an i7-3930). > > Boot stops just at: > > tsc: Refined TSC clocksource calibration: 2494.225 MHz > clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x23f3ea95b09, max_idle_ns: 440795287034 ns Uhhuh. So for Alexander Troy, just getting rid of the -march=core2 fixed the boot. But not for you. Strange. It really looked like the exact same thing. > This is a "Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz" with gcc-6.4 Yeah, other reporters of this have used gcc-6.4.0 too. But there's been some muddying of the waters there too - changing compilers have fixed it for some cases, but there's at least one report that a kernel build with gcc-7.2.0 still had the issue (and another that said it didn't). But the MCORE2 was consistent for several people - including you. Until this point. Strange. The only other thing (apart from the compiler flag) that MCORE2 results in is to enable CONFIG_X86_INTEL_USERCOPY CONFIG_X86_USE_PPRO_CHECKSUM CONFIG_X86_P6_NOP and the two first of those shouldn't even matter on x86-64, and I don't see that last one making any difference either. So because it looks so impossible that the "-march=core2" didn't make a difference for you, I'll ask you to please double-check that you actually booted into the right kernel. Sorry for doubting you, but your report just broke the _one_ consistent thing we've seen about this bug. Linus