From: Andi Kleen <ak@linux.intel.com>
To: Richard Weinberger <richard@nod.at>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Borislav Petkov <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124
Date: Wed, 16 Apr 2014 06:12:57 -0700 [thread overview]
Message-ID: <20140416131257.GF32556@tassilo.jf.intel.com> (raw)
In-Reply-To: <534E49C8.7050206@nod.at>
> [<ffffffff810349ab>] local_apic_timer_interrupt+0x3b/0x60
> [<ffffffff815903d5>] smp_apic_timer_interrupt+0x45/0x60
> [<ffffffff8158f18a>] apic_timer_interrupt+0x6a/0x70
> <EOI> [<ffffffff81581bd1>] ? panic+0x1a7/0x1ea
> [<ffffffff81581bcd>] ? panic+0x1a3/0x1ea
You're using panic_on_oops?
That seems like a bug in panic. It shouldn't reenable interrupts
-Andi
> [<ffffffff81586df4>] oops_end+0xd4/0xf0
> [<ffffffff8104299e>] no_context+0x12e/0x200
> [<ffffffff81042b8d>] __bad_area_nosemaphore+0x11d/0x220
> [<ffffffff81042cfe>] bad_area+0x4e/0x60
> [<ffffffff815898e0>] __do_page_fault+0x430/0x490
> [<ffffffff810a4d85>] ? call_console_drivers.clone.2+0xa5/0x100
> [<ffffffff811192b9>] ? irq_work_queue+0x69/0xc0
> [<ffffffff810a46a4>] ? wake_up_klogd+0x34/0x40
> [<ffffffff810a51bd>] ? console_unlock+0x24d/0x280
> [<ffffffff81589a1c>] do_page_fault+0xc/0x10
> [<ffffffff815862a2>] page_fault+0x22/0x30
> [<ffffffff81350206>] ? sysrq_handle_crash+0x16/0x20
> [<ffffffff81350b79>] __handle_sysrq+0x129/0x190
> [<ffffffff81350c1d>] write_sysrq_trigger+0x3d/0x40
> [<ffffffff811edc93>] proc_reg_write+0x43/0x70
> [<ffffffff81189b84>] vfs_write+0xc4/0x1e0
> [<ffffffff81189d86>] SyS_write+0x56/0xd0
> [<ffffffff810e3d56>] ? __audit_syscall_exit+0x216/0x2c0
> [<ffffffff8158e5d2>] system_call_fastpath+0x16/0x1b
next prev parent reply other threads:[~2014-04-16 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 9:13 WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124 Richard Weinberger
2014-04-16 9:21 ` Peter Zijlstra
2014-04-16 9:28 ` Richard Weinberger
2014-04-16 9:53 ` Steven Rostedt
2014-04-16 9:58 ` Peter Zijlstra
2014-04-16 13:12 ` Andi Kleen [this message]
2014-04-16 13:20 ` Richard Weinberger
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=20140416131257.GF32556@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=seiji.aguchi@hds.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