From: Fengguang Wu <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: 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, Dave Jones <davej@redhat.com>
Subject: Re: [perf] BUG: unable to handle kernel NULL pointer dereference at 00000085
Date: Tue, 7 Oct 2014 16:40:44 +0800 [thread overview]
Message-ID: <20141007084044.GA12300@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20141007081732.GF19379@twins.programming.kicks-ass.net>
On Tue, Oct 07, 2014 at 10:17:32AM +0200, Peter Zijlstra wrote:
> On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
> > > What is lacking is the actual .config.
> >
> > Sorry, attached the .config. I expected the script to auto attach it,
> > but obviously it's not yet perfect and failed to attach .config in
> > this case.
>
> Sure no problem, just figured I'd tell you.
>
> > > Also the times above (~285 seconds) seem to suggest userspace needs to
> > > do something ?
> >
> > It's trinity. I'll try upgrade it, but it seems be valid for trinity
> > to feed kernel with any parameters that it can accept -- unless the
> > kernel completely rejects it one day.
>
> OK, does it make sense to augment that script you have with a trinity
> parameter? Maybe have that userspace read the kernel cmdline and also
> run trinity when observed? That way you can provide full
> reproduction environments, which it appears you're striving towards.
The trinity binary is included in the initrd image that it downloads,
and will auto run after boot up. I also plan to add trinity as a LKP
test case. :)
Thanks,
Fengguang
prev parent reply other threads:[~2014-10-07 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:46 [perf] BUG: unable to handle kernel NULL pointer dereference at 00000085 Fengguang Wu
2014-10-04 17:24 ` Peter Zijlstra
2014-10-07 4:56 ` Fengguang Wu
2014-10-07 5:03 ` Fengguang Wu
2014-10-07 8:17 ` Peter Zijlstra
2014-10-07 8:40 ` 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=20141007084044.GA12300@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=davej@redhat.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=peterz@infradead.org \
--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