From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752743AbcGYJYn (ORCPT ); Mon, 25 Jul 2016 05:24:43 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34303 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751718AbcGYJYf (ORCPT ); Mon, 25 Jul 2016 05:24:35 -0400 From: Nicolai Stange To: Borislav Petkov Cc: Nicolai Stange , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start References: <20160724150549.2833-1-nicstange@gmail.com> <20160725070648.GB24576@nazgul.tnic> Date: Mon, 25 Jul 2016 11:24:31 +0200 In-Reply-To: <20160725070648.GB24576@nazgul.tnic> (Borislav Petkov's message of "Mon, 25 Jul 2016 09:06:48 +0200") Message-ID: <87bn1m5auo.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Borislav Petkov writes: > On Sun, Jul 24, 2016 at 05:05:49PM +0200, Nicolai Stange wrote: >> On x86_64 with CONFIG_RANDOMIZE_MEMORY and CONFIG_MICROCODE_INTEL, >> I get the following splat upon booting on an Intel i7-4800MQ: > > Before we dive into this, let's establish which tree you're exactly > testing... I tested on linux-next-20160722 (I wrote this below the '---' marker). > >> >> Call Trace: >> [] ? find_microcode_patch+0x4a/0xa0 >> [] load_microcode.isra.1.constprop.12+0x37/0xa0 >> [...] >> [] load_ucode_intel_ap+0x5d/0x80 >> [] load_ucode_ap+0x94/0xa0 >> [] cpu_init+0x58/0x3e0 >> [] ? set_pte_vaddr+0x5c/0x90 >> [] trap_init+0x2b6/0x328 >> [] start_kernel+0x224/0x47f >> [] ? early_idt_handler_array+0x120/0x120 >> [] x86_64_start_reservations+0x29/0x2b >> [] x86_64_start_kernel+0x14d/0x170 >> [...] >> RIP [] has_newer_microcode+0x5/0x20 >> [...] >> ---[ end trace b163fd3960fd46fb ]--- >> Kernel panic - not syncing: Attempted to kill the idle task! >> ---[ end Kernel panic - not syncing: Attempted to kill the idle task! >> >> It can be bisected to commit 21ef9a5c3164 ("Merge branch 'x86/microcode'"). > > This commit 21ef9a5c3164 does not exist - the current merge commit > corresponding to this is > > commit 2a2a745e2d248498a21ba3876d2481e90c7fe0a5 > Merge: caaaa222620c eb06158ee145 > Author: Ingo Molnar > Date: Sun Jul 24 08:26:41 2016 +0200 > > Merge branch 'x86/microcode' > >> Both of its parents, i.e. >> commit f5846c92b0a5 ("Merge branch 'x86/headers'") > > This commit does not exist either. > >> and >> commit eb06158ee145 ("x86/microcode: Remove unused symbol exports") > > This one does. > >> work fine by themselves. >> "Cross-bisecting" between v4.7-rc6..f5846c92b0a5 and v4.7-rc6..eb06158ee145 >> reveals the conflicting commits: >> commit 021182e52fe0 ("x86/mm: Enable KASLR for physical mapping memory >> regions") >> and >> commit 6c5456474e7f ("x86/microcode: Fix loading precedence"). > > Those two too. > > So it seems you're either testing an older tip/master or some linux-next. See above. > So let's clarify what exactly you're testing before we do anything else. If you want me to try any particular tree, please just tell me which one. Thanks, Nicolai