[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140417213012.GC27852@pd.tnic>
Date: Thu, 17 Apr 2014 23:30:12 +0200
From: Borislav Petkov <bp@...en8.de>
To: Owen Kibel <qmewlo@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Josh Boyer <jwboyer@...oraproject.org>,
"Luck, Tony" <tony.luck@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"hpa@...or.com" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"atodorov@...hat.com" <atodorov@...hat.com>,
"gong.chen@...ux.intel.com" <gong.chen@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/urgent] x86/mce: Fix CMCI preemption bugs
On Thu, Apr 17, 2014 at 02:21:41PM -0700, Owen Kibel wrote:
> The patch tested was from Chen, Gong
>
> https://lkml.org/lkml/2014/4/15/838
>
> It worked, apart from the warning on boot described previously - the
> possible boot message was extracted from /var/log/kern.log
>
> The above patch on mainline: 3.15-rc1 2014-04-13 [tar.xz]
>
> seems to have cured the problem
Ok, good. So this is straightened out.
@Ingo: just pick up Gong's fix without the raw_spin_lock* stuff.
> - the kernel appears fine after announcing something like
>
> kernel: [ 7.341085] BUG: using __this_cpu_write() in preemptible
> [00000000] code: modprobe/546
>
> in the boot process.
This is most likely unrelated and is caused by the preemption checks
added to __this_cpu_* in 188a81409ff7. If you'd like to debug this
further, please send a full dmesg:
dmesg > dmesg.log
Privately is fine too.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists