From: Borislav Petkov <bp@alien8.de>
To: Corey Minyard <minyard@acm.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Corey Minyard <cminyard@mvista.com>
Subject: Re: [PATCH][RT] x86: Fix an RT MCE crash
Date: Thu, 30 Jun 2016 19:01:34 +0200 [thread overview]
Message-ID: <20160630170134.GA3932@pd.tnic> (raw)
In-Reply-To: <57754B71.2000108@acm.org>
On Thu, Jun 30, 2016 at 11:40:17AM -0500, Corey Minyard wrote:
> I'm not sure. I've included the entire boot log below...
...
> [ 0.164185] [<ffffffff8106dcd8>] try_to_wake_up+0x28/0x320
> [ 0.164188] [<ffffffff8106dfe0>] wake_up_process+0x10/0x20
> [ 0.164207] [<ffffffff8101c548>] mce_notify_irq+0x28/0x30
> [ 0.164210] [<ffffffff8101df35>] intel_threshold_interrupt+0xb5/0xd0
> [ 0.164213] [<ffffffff8101e88c>] smp_threshold_interrupt+0x1c/0x40
> [ 0.164221] [<ffffffff816f9b5a>] threshold_interrupt+0x6a/0x70
> [ 0.164223] <EOI>
> [ 0.164226] [<ffffffff8101dda7>] ? cmci_recheck+0x67/0x70
> [ 0.164241] [<ffffffff816e9777>] setup_local_APIC+0x276/0x283
> [ 0.164259] [<ffffffff81caf010>] native_smp_prepare_cpus+0x379/0x43b
> [ 0.164266] [<ffffffff81ca3e4f>] kernel_init_freeable+0xd7/0x21a
> [ 0.164270] [<ffffffff816df1f0>] ? rest_init+0x90/0x90
> [ 0.164272] [<ffffffff816df1f9>] kernel_init+0x9/0x180
> [ 0.164275] [<ffffffff816f8dc8>] ret_from_fork+0x58/0x90
> [ 0.164277] [<ffffffff816df1f0>] ? rest_init+0x90/0x90
> [ 0.164295] Code: e7 ff ff 48 8b 7d 08 e8 02 1a 95 ff 5d c3 55 48 89 e5
> 41 54 53 48 89 fb 9c 41 5c fa bf 01 00 00 00 e8 a8 38 00 00 ba 00 01 00 00
> <f0> 66 0f c1 13 0f b6 ce 38 d1 74 10 0f 1f 80 00 00 00 00 f3 90
> [ 0.164298] RIP [<ffffffff816f344d>] _raw_spin_lock_irqsave+0x1d/0x50
> [ 0.164298] RSP <ffff88017fa03f00>
> [ 0.164299] CR2: 0000000000000600
> [ 0.656225] ---[ end trace 0000000000000001 ]---
> [ 0.656233] Kernel panic - not syncing: Fatal exception in interrupt
Hmm, we have that setup_local_APIC -> cmci_recheck path on latest kernel
too. However, we do init CMCI earlier, down the start_kernel() path.
Would it be possible to boot latest upstream kernel on it to see whether
it explodes the same way?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-06-30 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:24 [PATCH][RT] x86: Fix an RT MCE crash minyard
2016-06-30 13:43 ` Steven Rostedt
2016-06-30 14:49 ` Corey Minyard
2016-06-30 15:51 ` Steven Rostedt
2016-06-30 15:58 ` Corey Minyard
2016-06-30 16:01 ` Borislav Petkov
2016-06-30 16:17 ` Luck, Tony
2016-06-30 16:40 ` Corey Minyard
2016-06-30 17:01 ` Borislav Petkov [this message]
2016-06-30 17:18 ` Corey Minyard
2016-06-30 17:26 ` Borislav Petkov
2016-06-30 17:54 ` Corey Minyard
2016-06-30 18:22 ` Borislav Petkov
2016-06-30 19:44 ` Corey Minyard
2016-06-30 20:34 ` Borislav Petkov
2016-06-30 22:47 ` Corey Minyard
2016-07-01 7:20 ` Borislav Petkov
2016-07-06 0:59 ` Corey Minyard
2016-07-06 8:37 ` Borislav Petkov
2016-07-06 12:03 ` Corey Minyard
2016-07-06 13:32 ` Steven Rostedt
2016-07-06 13:43 ` Sebastian Andrzej Siewior
2016-07-11 17:32 ` Steven Rostedt
2016-07-01 9:20 ` Daniel Wagner
2016-06-30 16:04 ` Corey Minyard
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=20160630170134.GA3932@pd.tnic \
--to=bp@alien8.de \
--cc=cminyard@mvista.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=minyard@acm.org \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
/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.