From: kbuild test robot <lkp@intel.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, dzickus@redhat.com,
uobergfe@redhat.com, atomlin@redhat.com, mhocko@suse.cz,
fweisbec@gmail.com, tj@kernel.org, hidehiro.kawai.ez@hitachi.com,
cmetcalf@ezchip.com
Subject: Re: [PATCH 01/31] Add hard/soft lockup debugger entry points
Date: Fri, 29 Jan 2016 04:35:21 +0800 [thread overview]
Message-ID: <201601290439.TS8Esf3v%fengguang.wu@intel.com> (raw)
In-Reply-To: <1454010366-28416-1-git-send-email-jeffmerkey@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi Jeffrey,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160128]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-hard-soft-lockup-debugger-entry-points/20160129-035852
config: alpha-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=alpha
All errors (new ones prefixed by >>):
kernel/watchdog.c: In function 'watchdog_timer_fn':
>> kernel/watchdog.c:489:4: error: implicit declaration of function 'arch_breakpoint' [-Werror=implicit-function-declaration]
arch_breakpoint();
^
cc1: some warnings being treated as errors
vim +/arch_breakpoint +489 kernel/watchdog.c
483 if (regs)
484 show_regs(regs);
485 else
486 dump_stack();
487
488 if (debug_watchdog_lockups)
> 489 arch_breakpoint();
490
491 if (softlockup_all_cpu_backtrace) {
492 /* Avoid generating two back traces for current
---
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: 45062 bytes --]
next prev parent reply other threads:[~2016-01-28 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:46 Jeffrey Merkey
2016-01-28 19:56 ` Thomas Gleixner
2016-01-28 20:08 ` Jeffrey Merkey
2016-01-28 20:48 ` Thomas Gleixner
2016-01-28 20:58 ` Jeffrey Merkey
2016-01-28 22:06 ` Thomas Gleixner
2016-01-28 22:22 ` Jeffrey Merkey
2016-01-29 8:16 ` Ingo Molnar
2016-01-29 16:26 ` Jeffrey Merkey
2016-01-29 16:34 ` Jeffrey Merkey
2016-01-29 17:19 ` Jeffrey Merkey
2016-01-30 2:43 ` Jeffrey Merkey
2016-01-28 20:35 ` kbuild test robot [this message]
2016-01-28 20:41 ` Chris Metcalf
2016-01-28 20:48 ` Jeffrey Merkey
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=201601290439.TS8Esf3v%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=cmetcalf@ezchip.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jeffmerkey@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
--cc=uobergfe@redhat.com \
/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®