From: Tejun Heo <tj@kernel.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Christopher Lameter <cl@linux.com>,
Andre Wild <wild@linux.vnet.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: using __this_cpu_read() in preemptible [00000000] code: mm_percpu_wq/7
Date: Wed, 16 Aug 2017 07:20:43 -0700 [thread overview]
Message-ID: <20170816142042.GB4087514@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20170816091307.GA3102@osiris>
Hello,
On Wed, Aug 16, 2017 at 11:13:07AM +0200, Heiko Carstens wrote:
> [ 5968.010352] WARNING: CPU: 54 PID: 7 at kernel/workqueue.c:2041 process_one_work+0x6d4/0x718
>
> (I don't remember we have seen the warning above in the first report) and then
>
> [ 5968.010913] Kernel panic - not syncing: preempt check
> [ 5968.010919] CPU: 54 PID: 7 Comm: mm_percpu_wq Tainted: G W 4.13.0-rc4-dirty #3
> [ 5968.010923] Hardware name: IBM 3906 M03 703 (z/VM 6.4.0)
> [ 5968.010927] Workqueue: mm_percpu_wq vmstat_update
> [ 5968.010933] Call Trace:
> [ 5968.010937] ([<0000000000113fbe>] show_stack+0x8e/0xe0)
> [ 5968.010942] [<0000000000a514be>] dump_stack+0x96/0xd8
> [ 5968.010947] [<000000000014302a>] panic+0x102/0x248
> [ 5968.010952] [<00000000007836d8>] check_preemption_disabled+0xf8/0x110
> [ 5968.010956] [<00000000002ee8e2>] refresh_cpu_vm_stats+0x1b2/0x400
> [ 5968.010961] [<00000000002ef8be>] vmstat_update+0x2e/0x98
> [ 5968.010965] [<0000000000166374>] process_one_work+0x3d4/0x718
> [ 5968.010970] [<000000000016708c>] rescuer_thread+0x214/0x390
> [ 5968.010974] [<000000000016edbc>] kthread+0x16c/0x180
> [ 5968.010978] [<0000000000a7273a>] kernel_thread_starter+0x6/0xc
> [ 5968.010983] [<0000000000a72734>] kernel_thread_starter+0x0/0xc
>
> On cpu 54 we have mm_percpu_wq with:
>
> nr_cpus_allowed = 0x1,
> cpus_allowed = {
> bits = {0x4, 0x0, 0x0, 0x0}
> },
>
> We also have CONFIG_NR_CPUS=256, so the above translates to cpu 3, which
> obviously is not cpu 54 and explains the preempt check warning.
Looks like the same issue Paul was hitting.
http://lkml.kernel.org/r/1501541603-4456-3-git-send-email-paulmck@linux.vnet.ibm.com
Can you see whether the above patch helps?
Thank.s
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-08-16 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:05 Andre Wild
2017-07-12 15:44 ` Christopher Lameter
2017-07-12 16:13 ` Heiko Carstens
2017-08-16 9:13 ` Heiko Carstens
2017-08-16 14:20 ` Tejun Heo [this message]
2017-09-01 9:36 ` Andre Wild
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=20170816142042.GB4087514@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cl@linux.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wild@linux.vnet.ibm.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