From: Jeff Chua <jeff.chua.linux@gmail.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ming Lei <tom.leiming@gmail.com>,
Djalal Harouni <tixxdz@opendz.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Tony Luck <tony.luck@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@linux.intel.com>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
gouders@et.bocholt.fh-gelsenkirchen.de,
Marcos Souza <marcos.mage@gmail.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"tglx@linutronix.de" <tglx@linutronix.de>,
prasad@linux.vnet.ibm.com, justinmattock@gmail.com,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mel Gorman <mgorman@suse.de>,
Gilad Ben-Yossef <gilad@benyossef.com>
Subject: Re: x86/mce: machine check warning during poweroff
Date: Wed, 18 Jan 2012 00:15:38 +0800 [thread overview]
Message-ID: <CAAJw_ZtPZLPgi2z-0zB0n3hk9xzEbTnb1QGi1LjM5DC02t_W7A@mail.gmail.com> (raw)
In-Reply-To: <4F1544EA.5060907@linux.vnet.ibm.com>
On Tue, Jan 17, 2012 at 5:52 PM, Srivatsa S. Bhat
<srivatsa.bhat@linux.vnet.ibm.com> wrote:
> On 01/17/2012 07:51 AM, Suresh Siddha wrote:
>
>> On Sat, 2012-01-14 at 08:11 +0530, Srivatsa S. Bhat wrote:
>>> Of course, the warnings at drivers/base/core.c: device_release()
>>> as well as the IPI to offline cpu warnings still appear but are rather
>>> unrelated and harmless to the issue being discussed.
>>
>> As far the IPI offline cpu warnings are concerned, appended patch should
>> fix it. Can you please give it a try? Peterz, can you please review and
>> queue it after Srivatsa confirms that it works? Thanks.
>
>
> Hi Suresh,
>
> Thanks for the patch, but unfortunately it doesn't fix the problem!
> Exactly the same stack traces are seen during a CPU Hotplug stress test.
> (I didn't even have to stress it - it is so fragile that just a script
> to offline all cpus except the boot cpu was good enough to reproduce the
> problem easily.)
Works for me. But I'm still seeing this only during boot. Related?
Shall I bisect?
Freeing unused kernel memory: 520k freed
Write protecting the kernel read-only data: 8192k
Freeing unused kernel memory: 1140k freed
Freeing unused kernel memory: 464k freed
Adding 8290300k swap on /dev/sda3. Priority:-1 extents:1 across:8290300k SS
vmalloc: allocation failure: 0 bytes
modprobe: page allocation failure: order:0, mode:0xd2
Pid: 1914, comm: modprobe Not tainted 3.2.0 #6
Call Trace:
[<ffffffff8107c1ff>] ? 0xffffffff8107c1ff
[<ffffffff81061fec>] ? 0xffffffff81061fec
[<ffffffff8109ab6c>] ? 0xffffffff8109ab6c
[<ffffffff81061fec>] ? 0xffffffff81061fec
[<ffffffff8101bacc>] ? 0xffffffff8101bacc
[<ffffffff81061fec>] ? 0xffffffff81061fec
[<ffffffff81061fec>] ? 0xffffffff81061fec
[<ffffffff81062ec8>] ? 0xffffffff81062ec8
[<ffffffff810637c1>] ? 0xffffffff810637c1
[<ffffffff814d9cb9>] ? 0xffffffff814d9cb9
Mem-Info:
Node 0 DMA per-cpu:
CPU 0: hi: 0, btch: 1 usd: 0
CPU 1: hi: 0, btch: 1 usd: 0
CPU 2: hi: 0, btch: 1 usd: 0
CPU 3: hi: 0, btch: 1 usd: 0
Node 0 DMA32 per-cpu:
CPU 0: hi: 186, btch: 31 usd: 158
CPU 1: hi: 186, btch: 31 usd: 25
CPU 2: hi: 186, btch: 31 usd: 0
CPU 3: hi: 186, btch: 31 usd: 0
Node 0 Normal per-cpu:
CPU 0: hi: 186, btch: 31 usd: 93
CPU 1: hi: 186, btch: 31 usd: 74
CPU 2: hi: 186, btch: 31 usd: 170
CPU 3: hi: 186, btch: 31 usd: 60
active_anon:6162 inactive_anon:1 isolated_anon:0
active_file:1782 inactive_file:5164 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
free:1963131 slab_reclaimable:818 slab_unreclaimable:2728
mapped:1639 shmem:3 pagetables:292 bounce:0
Thanks,
Jeff
next prev parent reply other threads:[~2012-01-17 16:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:00 x86/mce: machine check warning during poweroff Djalal Harouni
2012-01-12 14:22 ` Ming Lei
2012-01-13 20:22 ` Srivatsa S. Bhat
2012-01-13 20:34 ` Justin P. Mattock
2012-01-13 20:37 ` Linus Torvalds
2012-01-13 20:53 ` Srivatsa S. Bhat
2012-01-13 21:08 ` Linus Torvalds
2012-01-13 21:24 ` Andi Kleen
2012-01-13 21:38 ` Justin P. Mattock
2012-01-13 22:06 ` Srivatsa S. Bhat
2012-01-13 22:17 ` Alan Stern
2012-01-13 22:18 ` Srivatsa S. Bhat
2012-01-13 23:13 ` Andi Kleen
2012-01-14 0:44 ` Dirk Gouders
2012-01-13 23:02 ` Linus Torvalds
2012-01-13 23:27 ` Srivatsa S. Bhat
2012-01-14 0:05 ` Linus Torvalds
2012-01-14 2:41 ` Srivatsa S. Bhat
2012-01-14 2:53 ` Linus Torvalds
2012-01-14 3:05 ` Srivatsa S. Bhat
2012-01-14 3:10 ` Linus Torvalds
2012-01-14 3:18 ` Srivatsa S. Bhat
2012-01-14 3:41 ` Linus Torvalds
2012-01-14 5:15 ` Tony Luck
2012-01-14 14:49 ` Greg KH
2012-01-14 16:30 ` Alan Stern
2012-01-14 20:45 ` Jeff Chua
2012-01-15 2:05 ` Tony Luck
2012-01-15 2:34 ` Greg KH
2012-01-15 3:36 ` Alan Stern
2012-01-16 18:15 ` Greg KH
2012-01-16 18:11 ` Greg KH
2012-01-16 18:27 ` Luck, Tony
2012-01-16 18:34 ` Greg KH
2012-01-16 18:42 ` Kay Sievers
2012-01-17 2:21 ` Suresh Siddha
2012-01-17 9:52 ` Srivatsa S. Bhat
2012-01-17 16:15 ` Jeff Chua [this message]
2012-01-17 16:36 ` Srivatsa S. Bhat
2012-01-18 3:17 ` Suresh Siddha
2012-01-18 10:19 ` Srivatsa S. Bhat
2012-01-18 13:15 ` Srivatsa S. Bhat
2012-01-18 13:32 ` Sergey Senozhatsky
2012-01-18 22:08 ` Suresh Siddha
2012-01-19 7:50 ` Sergey Senozhatsky
2012-01-19 12:02 ` Srivatsa S. Bhat
2012-01-20 2:28 ` Suresh Siddha
2012-01-23 8:43 ` Peter Zijlstra
2012-01-26 20:27 ` [tip:sched/urgent] sched/nohz: Fix nohz cpu idle load balancing state with cpu hotplug tip-bot for Suresh Siddha
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=CAAJw_ZtPZLPgi2z-0zB0n3hk9xzEbTnb1QGi1LjM5DC02t_W7A@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=borislav.petkov@amd.com \
--cc=gilad@benyossef.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=gregkh@suse.de \
--cc=justinmattock@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcos.mage@gmail.com \
--cc=mgorman@suse.de \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tixxdz@opendz.org \
--cc=tom.leiming@gmail.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).