mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Wei Jiangang <weijg.fnst@cn.fujitsu.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, x86@kernel.org,
	kexec@lists.infradead.org, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, ebiederm@xmission.com, fenghua.yu@intel.com,
	izumi.taku@jp.fujitsu.com,
	Wei Jiangang <weijg.fnst@cn.fujitsu.com>
Subject: Re: [PATCH] kexec: Fix kdump failure with notsc
Date: Thu, 7 Jul 2016 16:46:33 +0800	[thread overview]
Message-ID: <201607071617.dgK52iri%fengguang.wu@intel.com> (raw)
In-Reply-To: <1467876005-17292-1-git-send-email-weijg.fnst@cn.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Hi,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.7-rc6 next-20160706]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Wei-Jiangang/kexec-Fix-kdump-failure-with-notsc/20160707-152535
config: x86_64-randconfig-s5-07071541 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   arch/x86/kernel/machine_kexec_64.c: In function 'machine_kexec':
>> arch/x86/kernel/machine_kexec_64.c:272:33: error: implicit declaration of function 'lapic_disabled' [-Werror=implicit-function-declaration]
     if (image->preserve_context || lapic_disabled()) {
                                    ^~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/lapic_disabled +272 arch/x86/kernel/machine_kexec_64.c

   266		save_ftrace_enabled = __ftrace_enabled_save();
   267	
   268		/* Interrupts aren't acceptable while we reboot */
   269		local_irq_disable();
   270		hw_breakpoint_disable();
   271	
 > 272		if (image->preserve_context || lapic_disabled()) {
   273	#ifdef CONFIG_X86_IO_APIC
   274			/*
   275			 * We need to put APICs in legacy mode so that we can

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 30554 bytes --]

  reply	other threads:[~2016-07-07  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  7:20 Wei Jiangang
2016-07-07  8:46 ` kbuild test robot [this message]
2016-07-07 10:26   ` Wei, Jiangang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201607071617.dgK52iri%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ebiederm@xmission.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kbuild-all@01.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=weijg.fnst@cn.fujitsu.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®