Re: x86/mce: machine check warning during poweroff

[Srivatsa S. Bhat]

On 01/17/2012 09:45 PM, Jeff Chua wrote:

> On Tue, Jan 17, 2012 at 5:52 PM, Srivatsa S. Bhat
> <srivatsa.bhat@xxxxxxxxxxxxxxxxxx> 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


This is a different problem. Not the same as the one Suresh's patch
intended to fix. Your case has something to do with memory allocation
failures. The problem I am facing is Inter-Processor Interrupts (IPIs)
being sent to CPUs that are going offline, after selecting them as the
new ilb (Idle load balancer).

> 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
> 
>


Regards,
Srivatsa S. Bhat
IBM Linux Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/