All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [reboot] WARNING: CPU: 0 PID: 112 at kernel/events/core.c:5655 perf_swevent_add()
Date: Tue, 11 Mar 2014 10:33:12 +0800	[thread overview]
Message-ID: <20140311023312.GA9157@localhost> (raw)
In-Reply-To: <20140310125319.GE26334@krava.redhat.com>

Hi Jiri,

On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
> On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
> > 
> > Hi all,
> > 
> > This is a very old WARNING, too old to be bisectable. The below 3 different
> > back traces show that it's always triggered by trinity at system reboot time.
> > Any ideas to quiet it? Thank you!
> 
> hi,
> is there cpu hotplug involved? like writing to:
>   /sys/devices/system/cpu/cpu*/online

Yeah, we do run random CPU hotplug tests in the background.

Thanks,
Fengguang

      parent reply	other threads:[~2014-03-11  2:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08  6:51 [reboot] WARNING: CPU: 0 PID: 112 at kernel/events/core.c:5655 perf_swevent_add() Fengguang Wu
2014-03-08  6:56 ` [perf_swevent_init] BUG: unable to handle kernel paging request at b1793514 Fengguang Wu
2014-03-10 12:53 ` [reboot] WARNING: CPU: 0 PID: 112 at kernel/events/core.c:5655 perf_swevent_add() Jiri Olsa
2014-03-10 22:40   ` Jiri Olsa
2014-03-11  0:56     ` Jiri Olsa
2014-03-11 12:14       ` Fengguang Wu
2014-03-30 12:41         ` Fengguang Wu
2014-04-06 13:41           ` Jiri Olsa
2014-03-11  2:33   ` 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=20140311023312.GA9157@localhost \
    --to=fengguang.wu@intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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.