From: Borislav Petkov <bp@alien8.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: NOHZ: WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule
Date: Thu, 9 May 2013 14:50:40 +0200 [thread overview]
Message-ID: <20130509125040.GF27333@pd.tnic> (raw)
In-Reply-To: <alpine.LNX.2.00.1305091423460.23038@pobox.suse.cz>
On Thu, May 09, 2013 at 02:29:18PM +0200, Jiri Kosina wrote:
> Hi,
>
> I just got the warning below when resuming from hibernation with kernel
> that has NO_HZ_FULL_ALL=y. This is with topmost commit e0fd9affeb640.
Did you boot with any of the NO_HZ_FULL options on the command line,
i.e. rcu_nocbs?
Because I saw the same issue during boot when I was testing the
NO_HZ_FULL stuff previously:
Feb 21 11:13:17 gondor kernel: [ 0.093417] #3
Feb 21 11:13:17 gondor kernel: [ 0.106844] SMP alternatives: lockdep: fixing up alternatives
Feb 21 11:13:17 gondor kernel: [ 0.118060] ------------[ cut here ]------------
Feb 21 11:13:17 gondor kernel: [ 0.118069] WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule+0x58/0x60()
Feb 21 11:13:17 gondor kernel: [ 0.118069] Hardware name: Precision T3600
Feb 21 11:13:17 gondor kernel: [ 0.106955] #4
Feb 21 11:13:17 gondor kernel: [ 0.118070] Modules linked in:
Feb 21 11:13:17 gondor kernel: [ 0.118073] Pid: 0, comm: swapper/4 Not tainted 3.8.0-rc6+ #4
Feb 21 11:13:17 gondor kernel: [ 0.118074] Call Trace:
Feb 21 11:13:17 gondor kernel: [ 0.118076] [<ffffffff8103d35f>] warn_slowpath_common+0x7f/0xc0
Feb 21 11:13:17 gondor kernel: [ 0.118079] [<ffffffff8103d3ba>] warn_slowpath_null+0x1a/0x20
Feb 21 11:13:17 gondor kernel: [ 0.118081] [<ffffffff81024a58>] native_smp_send_reschedule+0x58/0x60
Feb 21 11:13:17 gondor kernel: [ 0.118083] [<ffffffff81071ba0>] wake_up_nohz_cpu+0x80/0x90
Feb 21 11:13:17 gondor kernel: [ 0.118086] [<ffffffff8104e611>] add_timer_on+0x91/0x110
Feb 21 11:13:17 gondor kernel: [ 0.118090] [<ffffffff8101ccab>] mce_start_timer.isra.12+0x6b/0x80
Feb 21 11:13:17 gondor kernel: [ 0.118092] [<ffffffff8101cd1d>] __mcheck_cpu_init_timer+0x5d/0x70
Feb 21 11:13:17 gondor kernel: [ 0.118094] [<ffffffff815cc466>] mcheck_cpu_init+0x36b/0x400
Feb 21 11:13:17 gondor kernel: [ 0.118097] [<ffffffff815ca15b>] identify_cpu+0x39d/0x3d0
Feb 21 11:13:17 gondor kernel: [ 0.118099] [<ffffffff815ca1a2>] identify_secondary_cpu+0x14/0x1b
Feb 21 11:13:17 gondor kernel: [ 0.118101] [<ffffffff815cd008>] smp_store_cpu_info+0x38/0x3a
Feb 21 11:13:17 gondor kernel: [ 0.118103] [<ffffffff815cd550>] start_secondary+0xfb/0x1f7
Feb 21 11:13:17 gondor kernel: [ 0.118121] ---[ end trace 8ffeaaf1f7048154 ]---
And I *think* I saw this yesterday too on a randbuild kernel.
Looks like we're sending a resched IPI to a cpu which is not online yet
in order to start the MCE polling timer. So the rcu* options are kinda
unlikely to be related, AFAICT.
Frederic?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-05-09 12:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 12:29 NOHZ: WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule Jiri Kosina
2013-05-09 12:50 ` Borislav Petkov [this message]
2013-05-09 12:58 ` Borislav Petkov
2013-05-15 18:45 ` Paul E. McKenney
2013-05-15 22:43 ` Borislav Petkov
2013-05-15 23:55 ` Paul E. McKenney
2013-05-17 13:56 ` NOHZ: WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule, round 2 Borislav Petkov
2013-05-20 3:16 ` Michael Wang
2013-05-20 4:50 ` Borislav Petkov
2013-05-20 6:23 ` Michael Wang
2013-05-20 6:47 ` Borislav Petkov
2013-05-20 6:58 ` Michael Wang
2013-05-20 7:06 ` Michael Wang
2013-05-20 7:12 ` Viresh Kumar
2013-05-20 7:25 ` Michael Wang
2013-05-20 8:56 ` Michael Wang
2013-05-20 9:09 ` Viresh Kumar
2013-05-20 9:24 ` Michael Wang
2013-05-20 13:23 ` Borislav Petkov
2013-05-20 13:43 ` Viresh Kumar
2013-05-20 15:08 ` Borislav Petkov
2013-05-21 2:20 ` Michael Wang
2013-05-21 2:37 ` Michael Wang
2013-05-21 7:21 ` Borislav Petkov
2013-05-21 7:58 ` Michael Wang
2013-05-20 7:36 ` Tejun Heo
2013-05-20 8:10 ` Frederic Weisbecker
2013-05-20 9:31 ` Srivatsa S. Bhat
2013-05-20 9:40 ` Viresh Kumar
2013-05-20 10:24 ` Viresh Kumar
2013-06-04 21:20 ` Jiri Kosina
2013-06-05 2:30 ` Michael Wang
2013-06-05 8:08 ` Jiri Kosina
2013-06-05 8:12 ` Michael Wang
2013-05-10 0:29 ` NOHZ: WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule Frederic Weisbecker
2013-05-10 9:28 ` Borislav Petkov
2013-05-10 9:26 ` Frederic Weisbecker
2013-05-10 9:37 ` Ingo Molnar
2013-05-10 9:45 ` Borislav Petkov
2013-05-10 15:31 ` Frederic Weisbecker
2013-05-10 9:43 ` Borislav Petkov
2013-05-10 15:42 ` Jiri Kosina
2013-05-10 15:03 ` Jiri Kosina
2013-05-10 15:21 ` Borislav Petkov
2013-05-10 15:43 ` Frederic Weisbecker
2013-05-10 16:23 ` Borislav Petkov
2013-05-10 21:38 ` Frederic Weisbecker
2013-05-13 14:56 ` Jiri Kosina
2013-05-13 19:40 ` Thomas Gleixner
2013-05-13 20:01 ` Jiri Kosina
2013-05-14 15:46 ` [tip:timers/urgent] tick: Don't invoke tick_nohz_stop_sched_tick( ) if the cpu is offline tip-bot for Thomas Gleixner
2013-05-15 19:41 ` Frederic Weisbecker
2013-05-16 14:06 ` Thomas Gleixner
2013-05-16 14:15 ` Borislav Petkov
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=20130509125040.GF27333@pd.tnic \
--to=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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