Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751801AbbHSGP1 (ORCPT ); Wed, 19 Aug 2015 02:15:27 -0400 Received: from mail-wi0-f174.google.com ([209.85.212.174]:37380 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751207AbbHSGPZ (ORCPT ); Wed, 19 Aug 2015 02:15:25 -0400 Date: Wed, 19 Aug 2015 08:15:21 +0200 From: Ingo Molnar To: "H. Peter Anvin" Cc: Linus Torvalds , Juergen Gross , Andy Lutomirski , Linux Kernel Mailing List , Thomas Gleixner , Peter Zijlstra , Brian Gerst , Denys Vlasenko , Andrew Morton Subject: Re: [GIT PULL] x86 fixes Message-ID: <20150819061521.GA28292@gmail.com> References: <20150814071500.GA2678@gmail.com> <20150817080143.GA16928@gmail.com> <55D25D7F.40503@zytor.com> <20150819055931.GD32338@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150819055931.GD32338@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3918 Lines: 46 * Ingo Molnar wrote: > So I went and built 743aa456c1834f76 with ARCH=i386 defconfig +MATH_EMULATION=y > and booted it on real hardware with and without 'no387': > > - 743aa456c1834f76: boots fine to a generic distro > - 743aa456c1834f76 + no387: early crash > > the early crash is similar to what I saw when doing the recent FPU changes (and > which crash I fixed): Hm, so that crash is back again with the latest kernel: [ 0.000000] EIP is at kmem_cache_alloc+0x25/0x110 ... [ 0.000000] [] init_fpu+0x7f/0xc0 [ 0.000000] [] math_emulate+0x6b5/0xc90 [ 0.000000] [] ? early_serial_putc+0x60/0x60 [ 0.000000] [] ? call_console_drivers.constprop.14+0x8c/0xe0 [ 0.000000] [] ? up+0x25/0x50 [ 0.000000] [] ? console_unlock+0x305/0x4d0 [ 0.000000] [] ? process_srcu+0x56/0xb0 [ 0.000000] [] ? do_debug+0x160/0x160 [ 0.000000] [] do_device_not_available+0x38/0x60 [ 0.000000] [] error_code+0x5a/0x60 [ 0.000000] [] ? do_debug+0x160/0x160 [ 0.000000] [] ? fpu_init+0xd9/0xf7 [ 0.000000] [] cpu_init+0x237/0x23f [ 0.000000] [] trap_init+0x243/0x24b [ 0.000000] [] start_kernel+0x143/0x2d4 [ 0.000000] [] i386_start_kernel+0x76/0x7b I suspect due to: 5aaeb5c01c5b x86/fpu, sched: Introduce CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT and use it on x86 0c8c0f03e3a2 x86/fpu, sched: Dynamically allocate 'struct fpu' Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/