From: Fengguang Wu <fengguang.wu@intel.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ingo Molnar <mingo@kernel.org>, Jet Chen <jet.chen@intel.com>,
Su Tao <tao.su@intel.com>, Yuanhan Liu <yuanhan.liu@intel.com>,
LKP <lkp@01.org>,
linux-kernel@vger.kernel.org
Subject: Re: [hw_breakpoint] WARNING: at kernel/trace/trace_kprobe.c:1393 kprobe_trace_self_tests_init()
Date: Wed, 1 Oct 2014 14:57:57 +0800 [thread overview]
Message-ID: <20141001065757.GA17297@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20140930175844.GA20922@redhat.com>
Hi Oleg,
> > +-----------------------------------------------------------------------+------------+------------+------------------+
> > | | 003002e04e | 8b4d801b2b | v3.17-rc7_093000 |
> > +-----------------------------------------------------------------------+------------+------------+------------------+
> > | boot_successes | 60 | 0 | 0 |
> > | boot_failures | 0 | 20 | 11 |
> > | WARNING:at_kernel/trace/trace_kprobe.c:kprobe_trace_self_tests_init() | 0 | 20 | 11 |
> > | backtrace:kprobe_trace_self_tests_init | 0 | 20 | 11 |
> > | backtrace:warn_slowpath_null | 0 | 20 | 11 |
> > | backtrace:kernel_init_freeable | 0 | 20 | 11 |
> > +-----------------------------------------------------------------------+------------+------------+------------------+
> >
> > [ 4.188679] Testing kprobe tracing:
> > [ 4.189810] Could not insert probe at kprobe_trace_selftest_target+0: -22
>
> __register_trace_kprobe() fails.
>
> No, I am very sure this can't be caused by the commit above. If nothing else,
> task_bp_pinned() changed by this commit is not even called in this case.
Sorry it is a bad bisect -- debug shows that CONFIG_FTRACE_STARTUP_TEST
is not enabled at all in the parent commit, which makes it boot success.
I'll fix this issue in my script and make the bisect stable.
Thanks,
Fengguang
prev parent reply other threads:[~2014-10-01 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:43 Fengguang Wu
2014-09-30 17:58 ` Oleg Nesterov
2014-10-01 2:18 ` Masami Hiramatsu
2014-10-01 6:57 ` Fengguang Wu [this message]
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=20141001065757.GA17297@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tao.su@intel.com \
--cc=yuanhan.liu@intel.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®