From: Steven Rostedt <rostedt@goodmis.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [trace] kernel BUG at kernel/sched/core.c:2881!
Date: Thu, 2 Jul 2015 15:56:47 -0400 [thread overview]
Message-ID: <20150702155647.693ad4d6@gandalf.local.home> (raw)
In-Reply-To: <20150630141803.GA28071@wfg-t540p.sh.intel.com>
On Tue, 30 Jun 2015 22:18:03 +0800
Fengguang Wu <fengguang.wu@intel.com> wrote:
> Hi Rostedt,
>
> FYI, this merge changes kernel crash to some more obvious kernel BUG
> message. If it's still not helpful, I can try bisect the old crash
> or split up the merge and bisect into them.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit e382608254e06c8109f40044f5e693f2e04f3899
Hmm, I'm able to trigger this bug all the way back to 3.19 (I'll try
further). Something about this config makes the branch tracer crash.
-- Steve
next prev parent reply other threads:[~2015-07-02 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:18 Fengguang Wu
2015-07-02 19:56 ` Steven Rostedt [this message]
2015-07-07 15:06 ` Steven Rostedt
2015-07-07 19:03 ` Steven Rostedt
2015-07-07 22:37 ` Steven Rostedt
2015-07-08 3:57 ` 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=20150702155647.693ad4d6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@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 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®