From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: Re: [perf/x86/RAPL] BUG: unable to handle kernel NULL pointer dereference at 00000028
Date: Fri, 01 Aug 2014 07:59:42 +0800 [thread overview]
Message-ID: <20140731235942.GA5635@localhost> (raw)
In-Reply-To: <CABPqkBQ5WagvWLa4ojLAZB2fgBUa53YstBsmLS6JqVzjZ2aEaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On Thu, Jul 31, 2014 at 07:57:25PM +0200, Stephane Eranian wrote:
> On Thu, Jul 31, 2014 at 4:32 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Hi Stephane,
> >
> > On Wed, Jul 30, 2014 at 07:56:11PM +0200, Stephane Eranian wrote:
> >> On Wed, Jul 30, 2014 at 7:53 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> >> > On Wed, Jul 30, 2014 at 06:45:58AM +0200, Stephane Eranian wrote:
> >> >> On Wed, Jul 30, 2014 at 6:00 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> >> >> > Greetings,
> >> >> >
> >> >> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >> >> >
> >> >> Is this booting a guest kernel or native?
> >> >
> >> > It's a guest kernel.
> >> >
> >> >> What is the host CPU?
> >> >
> >> > The host CPU is E5-2680, Sandy Bridge-EP.
> >> >
> >> I thought this problem had already be mentioned a while back.
> >>
> >> See https://lkml.org/lkml/2014/3/6/685
> >> And https://lkml.org/lkml/2014/4/23/512
> >>
> >> So what you are telling here is that those two fixes never made it or
> >> that you are
> >> running an older kernel.
> >
> > I just checked linux-next and find that the bug in rapl_pmu_init() has
> > been fixed. linux-next happen to have the same "BUG: unable to handle
> > kernel NULL pointer dereference" message but at another function
> > validate_chain().. Attached is the dmesg in linux-next.
> >
> > Sorry for the noise!
> >
> Is it fixed with the two patches I referred you to?
Yes.
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: 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>, LKML <linux-kernel@vger.kernel.org>,
Venkatesh Srinivas <venkateshs@google.com>
Subject: Re: [perf/x86/RAPL] BUG: unable to handle kernel NULL pointer dereference at 00000028
Date: Fri, 1 Aug 2014 07:59:42 +0800 [thread overview]
Message-ID: <20140731235942.GA5635@localhost> (raw)
In-Reply-To: <CABPqkBQ5WagvWLa4ojLAZB2fgBUa53YstBsmLS6JqVzjZ2aEaQ@mail.gmail.com>
On Thu, Jul 31, 2014 at 07:57:25PM +0200, Stephane Eranian wrote:
> On Thu, Jul 31, 2014 at 4:32 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Hi Stephane,
> >
> > On Wed, Jul 30, 2014 at 07:56:11PM +0200, Stephane Eranian wrote:
> >> On Wed, Jul 30, 2014 at 7:53 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> >> > On Wed, Jul 30, 2014 at 06:45:58AM +0200, Stephane Eranian wrote:
> >> >> On Wed, Jul 30, 2014 at 6:00 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> >> >> > Greetings,
> >> >> >
> >> >> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >> >> >
> >> >> Is this booting a guest kernel or native?
> >> >
> >> > It's a guest kernel.
> >> >
> >> >> What is the host CPU?
> >> >
> >> > The host CPU is E5-2680, Sandy Bridge-EP.
> >> >
> >> I thought this problem had already be mentioned a while back.
> >>
> >> See https://lkml.org/lkml/2014/3/6/685
> >> And https://lkml.org/lkml/2014/4/23/512
> >>
> >> So what you are telling here is that those two fixes never made it or
> >> that you are
> >> running an older kernel.
> >
> > I just checked linux-next and find that the bug in rapl_pmu_init() has
> > been fixed. linux-next happen to have the same "BUG: unable to handle
> > kernel NULL pointer dereference" message but at another function
> > validate_chain().. Attached is the dmesg in linux-next.
> >
> > Sorry for the noise!
> >
> Is it fixed with the two patches I referred you to?
Yes.
Thanks,
Fengguang
next prev parent reply other threads:[~2014-07-31 23:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 4:00 [perf/x86/RAPL] BUG: unable to handle kernel NULL pointer dereference at 00000028 Fengguang Wu
2014-07-30 4:00 ` Fengguang Wu
2014-07-30 4:45 ` Stephane Eranian
2014-07-30 4:45 ` Stephane Eranian
2014-07-30 5:53 ` Fengguang Wu
2014-07-30 5:53 ` Fengguang Wu
2014-07-30 17:56 ` Stephane Eranian
2014-07-30 17:56 ` Stephane Eranian
2014-07-31 2:32 ` Fengguang Wu
2014-07-31 2:32 ` Fengguang Wu
2014-07-31 17:57 ` Stephane Eranian
2014-07-31 17:57 ` Stephane Eranian
2014-07-31 23:59 ` Fengguang Wu [this message]
2014-07-31 23:59 ` Fengguang Wu
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=20140731235942.GA5635@localhost \
--to=fengguang.wu@intel.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.