From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751932AbbINVuh (ORCPT ); Mon, 14 Sep 2015 17:50:37 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:48190 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061AbbINVug (ORCPT ); Mon, 14 Sep 2015 17:50:36 -0400 Subject: Re: Unable to link 4.3-rc1: undefined reference to `native_machine_crash_shutdown' To: Piotr Karbowski , linux-kernel@vger.kernel.org, X86 ML , "K. Y. Srinivasan" References: <55F73DB7.7010206@gmail.com> Cc: Greg Kroah-Hartman From: Randy Dunlap X-Enigmail-Draft-Status: N1110 Message-ID: <55F74129.3020702@infradead.org> Date: Mon, 14 Sep 2015 14:50:33 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55F73DB7.7010206@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/14/15 14:35, Piotr Karbowski wrote: > Hello, > > I wanted to try on the 4.3-rc1 kernel and it fails during linking with undefined reference to `native_machine_crash_shutdown' > > # make > CHK include/config/kernel.release > CHK include/generated/uapi/linux/version.h > CHK include/generated/utsrelease.h > CHK include/generated/bounds.h > CHK include/generated/timeconst.h > CHK include/generated/asm-offsets.h > CALL scripts/checksyscalls.sh > CHK include/generated/compile.h > CHK kernel/config_data.h > LINK vmlinux > LD vmlinux.o > MODPOST vmlinux.o > GEN .version > CHK include/generated/compile.h > UPD include/generated/compile.h > CC init/version.o > LD init/built-in.o > arch/x86/built-in.o: In function `hv_machine_crash_shutdown': > mshyperv.c:(.text+0x7514c): undefined reference to `native_machine_crash_shutdown' > Makefile:927: recipe for target 'vmlinux' failed > make: *** [vmlinux] Error 1 > > The dot config is as follow (stripped hashes and empty lines): > [deleted] This has been happening for awhile now and has been reported several times. Also there have been 2 or 3 patches posted to fix it... so what will it take to get a fix merged? anyone? thnx, -- ~Randy