From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "he, bo" <bo.he@intel.com>
Cc: akpm@linux-foundation.org, mingo@elte.hu, a.p.zijlstra@chello.nl,
rusty@rustcorp.com.au, william.douglas@intel.com,
linux-kernel@vger.kernel.org, yanmin_zhang@linux.intel.com,
yanmin.zhang@intel.com
Subject: Re: [PATCH] sched: fix OOPS when build_sched_domains percpu allocation fails
Date: Wed, 25 Apr 2012 18:29:28 +0530 [thread overview]
Message-ID: <4F97F530.8090005@linux.vnet.ibm.com> (raw)
In-Reply-To: <1335355161.5892.17.camel@hebo>
On 04/25/2012 05:29 PM, he, bo wrote:
> From: "he, bo" <bo.he@intel.com>
>
> Under extreme memory used up situation, percpu allocation
> might fails. We hit it when system go to suspend-to-ram.
>
> EIP: [<c124411a>] build_sched_domains+0x23a/0xad0
> SS:ESP 0068:de725d04
> CR2: 0000000034811000
> ---[ end trace d6086359b670b975 ]---
> Kernel panic - not syncing: Fatal exception
> Pid: 3026, comm: kworker/u:3 Tainted: G D W
> 3.0.8-137473-gf42fbef #1
> Call Trace:
> [<c18cc4f2>] panic+0x66/0x16c
> [<c12521a1>] ? oops_exit+0x61/0x90
> [<c1205f89>] oops_end+0xb9/0xd0
> [<c1227796>] no_context+0xc6/0x1f0
> [<c1227958>] __bad_area_nosemaphore+0x98/0x140
> [<c1204ebf>] ? dump_trace+0x7f/0xf0
> [<c1227d30>] ? pgtable_bad+0x130/0x130
> [<c1227a17>] bad_area_nosemaphore+0x17/0x20
> [<c1227fa0>] do_page_fault+0x270/0x3c0
> [<c1306afa>] ? pcpu_alloc+0x12ca/0x1300
> [<c1227d30>] ? pgtable_bad+0x130/0x130
> [<c1227d30>] ? pgtable_bad+0x130/0x130
> [<c18d09d3>] error_code+0x5f/0x64
> [<c13000d8>] ? shmem_setattr+0x198/0x230
> [<c1227d30>] ? pgtable_bad+0x130/0x130
> [<c124411a>] ? build_sched_domains+0x23a/0xad0
> [<c18d01a6>] ? _raw_spin_unlock_irqrestore+0x26/0x50
> [<c1244c37>] partition_sched_domains+0x287/0x4b0
> [<c12a77be>] cpuset_update_active_cpus+0x1fe/0x210
> [<c1673017>] ? __cpufreq_remove_dev+0x167/0x360
> [<c18cf03c>] ? down_write+0x1c/0x40
> [<c123712d>] cpuset_cpu_inactive+0x1d/0x30
> [<c127dff2>] notifier_call_chain+0x52/0x90
> [<c127e04e>] __raw_notifier_call_chain+0x1e/0x30
> [<c18b37c9>] _cpu_down+0x89/0x230
> [<c12547f9>] disable_nonboot_cpus+0x79/0x100
> [<c1299fb3>] suspend_devices_and_enter+0x133/0x2e0
> [<c129a27d>] enter_state+0x11d/0x180
> [<c129a307>] pm_suspend+0x27/0x70
> [<c129b8b6>] suspend+0x96/0x1d0
> [<c1271aa3>] process_one_work+0x103/0x400
> [<c129b820>] ? power_suspend_late+0x90/0x90
> [<c12728ac>] worker_thread+0x12c/0x4b0
> [<c123748d>] ? sub_preempt_count+0x3d/0x50
> [<c18d01a6>] ? _raw_spin_unlock_irqrestore+0x26/0x50
> [<c1272780>] ? manage_workers+0x520/0x520
> [<c1276f44>] kthread+0x74/0x80
> [<c1276ed0>] ? __init_kthread_worker+0x30/0x30
> [<c18d113a>] kernel_thread_helper+0x6/0x10
>
> Signed-off-by: he, bo <bo.he@intel.com>
> Reviewed-by: Zhang, Yanmin <yanmin.zhang@intel.com>
Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2012-04-25 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 11:59 [PATCH] sched: fix OOPS when build_sched_domains percpu allocation fails he, bo
2012-04-25 12:20 ` Peter Zijlstra
2012-04-25 12:59 ` Srivatsa S. Bhat [this message]
2012-04-26 11:56 ` [tip:sched/urgent] sched: Fix OOPS when build_sched_domains() " tip-bot for he, bo
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=4F97F530.8090005@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bo.he@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=william.douglas@intel.com \
--cc=yanmin.zhang@intel.com \
--cc=yanmin_zhang@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox