From: Fengguang Wu <fengguang.wu@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Chuansheng Liu <chuansheng.liu@intel.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [flow_cache_new_hashrnd] WARNING: at kernel/smp.c:328 smp_call_function_single()
Date: Mon, 11 Feb 2013 17:10:46 +0800 [thread overview]
Message-ID: <20130211091046.GA12094@localhost> (raw)
In-Reply-To: <20130211090309.GA23932@gmail.com>
On Mon, Feb 11, 2013 at 10:03:09AM +0100, Ingo Molnar wrote:
>
> * Fengguang Wu <fengguang.wu@intel.com> wrote:
>
> > Greetings,
> >
> > I got the below oops and the first bad commit is
>
> It's a one-time warning, not an actual crash, right?
Yes, it is.
Thanks,
Fengguang
prev parent reply other threads:[~2013-02-11 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 8:56 [flow_cache_new_hashrnd] WARNING: at kernel/smp.c:328 smp_call_function_single() Fengguang Wu
2013-02-11 9:03 ` Ingo Molnar
2013-02-11 9:10 ` 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=20130211091046.GA12094@localhost \
--to=fengguang.wu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=chuansheng.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).