From: Peter Zijlstra <peterz@infradead.org>
To: Don Zickus <dzickus@redhat.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Sasha Levin <levinsasha928@gmail.com>,
Josh Boyer <jwboyer@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>,
Suresh B Siddha <suresh.b.siddha@intel.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: WARNING: at arch/x86/kernel/smp.c:119 native_smp_send_reschedule+0x25/0x43()
Date: Fri, 10 Feb 2012 21:18:41 +0100 [thread overview]
Message-ID: <1328905121.25989.52.camel@laptop> (raw)
In-Reply-To: <20120210200250.GG5650@redhat.com>
On Fri, 2012-02-10 at 15:02 -0500, Don Zickus wrote:
> I also ran into the same problem you did and hacked up another patch that
> checked a global atomic variable that let the system know we were shutting
> down and not to do the WARN_ON (the global is already created for the NMI
> case now).
system_state seems like that thing..
next prev parent reply other threads:[~2012-02-10 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 1:31 WARNING: at arch/x86/kernel/smp.c:119 native_smp_send_reschedule+0x25/0x43() Sasha Levin
2012-02-09 0:59 ` Josh Boyer
2012-02-09 19:46 ` Sasha Levin
2012-02-10 10:06 ` Srivatsa S. Bhat
2012-02-10 18:58 ` Peter Zijlstra
2012-02-10 19:03 ` Peter Zijlstra
2012-02-10 20:02 ` Don Zickus
2012-02-10 20:18 ` Peter Zijlstra [this message]
2012-02-10 20:31 ` Don Zickus
2012-02-10 20:36 ` Peter Zijlstra
2012-02-10 21:04 ` Don Zickus
2012-03-23 10:47 ` Sasha Levin
2012-03-23 13:26 ` Don Zickus
2012-04-05 20:38 ` Tony Luck
2012-06-01 13:36 ` Borislav Petkov
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=1328905121.25989.52.camel@laptop \
--to=peterz@infradead.org \
--cc=avi@redhat.com \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=jwboyer@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sergey.senozhatsky@gmail.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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