From: Henrique de Moraes Holschuh <hmh@hmh.eng.br> To: Michael Wang <wangyun@linux.vnet.ibm.com> Cc: Ben Hutchings <ben@decadent.org.uk>, linux-kernel@vger.kernel.org, "paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com> Subject: Re: rcu_bh stalls on 3.2.28 Date: Mon, 3 Sep 2012 14:24:41 -0300 [thread overview] Message-ID: <20120903172441.GA19614@khazad-dum.debian.net> (raw) In-Reply-To: <50444897.6070803@linux.vnet.ibm.com> On Mon, 03 Sep 2012, Michael Wang wrote: > On 09/01/2012 07:02 AM, Henrique de Moraes Holschuh wrote: > > Just got one of these: > > > > kernel: INFO: rcu_bh detected stall on CPU 2 (t=0 jiffies) > > kernel: Pid: 0, comm: swapper/2 Not tainted 3.2.28+ #2 > > kernel: Call Trace: > > kernel: <IRQ> [<ffffffff810d1609>] __rcu_pending+0x159/0x400 > > kernel: [<ffffffff810d20bb>] rcu_check_callbacks+0x9b/0x120 > > kernel: [<ffffffff81089673>] update_process_times+0x43/0x80 > > kernel: [<ffffffff810a836f>] tick_sched_timer+0x5f/0xb0 > > kernel: [<ffffffff8109c097>] __run_hrtimer.isra.30+0x57/0x100 > > kernel: [<ffffffff8109c8f5>] hrtimer_interrupt+0xe5/0x220 > > kernel: [<ffffffff8104ce14>] smp_apic_timer_interrupt+0x64/0xa0 > > kernel: [<ffffffff8159b5cb>] apic_timer_interrupt+0x6b/0x70 > > kernel: <EOI> [<ffffffff81315645>] ? intel_idle+0xe5/0x140 > > kernel: [<ffffffff81315623>] ? intel_idle+0xc3/0x140 > > kernel: [<ffffffff814420ee>] cpuidle_idle_call+0x8e/0xf0 > > kernel: [<ffffffff81032425>] cpu_idle+0xa5/0x110 > > kernel: [<ffffffff8158a9ac>] start_secondary+0x1e5/0x1ec > > Hi, Henrique > > rsp->gp_start and rsp->jiffies_stall should already set before we start > check stall for this gp, but the INFO show that we have a current > jiffies which bigger then rsp->jiffies_stall but equal to rsp->gp_start, > really strange... > > Could you please have a try on the latest kernel and confirm whether > this issue still exist? It is a production box, it is difficult to run a -rc kernel there. And the stalls are very rare, too. That's the only one I got, so at this point I cannot tell you whether something fixed the problem or not, just try to give you clues if a stall does happen. > BTW: > Is this stall info comes from a virtual machine? No, it runs on baremetal. The box has one Xeon X5550 processor, 4 cores, 8 threads, and it is allowed to go into C1, C3 and C6 (which it does very very often). It might be some sort of race related to SMIs? The worst-case SMM-induced delay on this box is quite high (I don't recall if that means 150ms or 150us), as measured by the Intel BITS[1]. [1] http://biosbits.org/ -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
next prev parent reply other threads:[~2012-09-03 17:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-20 13:04 Linux 3.2.28 Ben Hutchings 2012-08-20 13:05 ` Ben Hutchings 2012-08-31 23:02 ` rcu_bh stalls on 3.2.28 Henrique de Moraes Holschuh 2012-09-03 6:05 ` Michael Wang 2012-09-03 17:24 ` Henrique de Moraes Holschuh [this message] 2012-09-09 18:12 ` Ben Hutchings
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=20120903172441.GA19614@khazad-dum.debian.net \ --to=hmh@hmh.eng.br \ --cc=ben@decadent.org.uk \ --cc=linux-kernel@vger.kernel.org \ --cc=paulmck@linux.vnet.ibm.com \ --cc=wangyun@linux.vnet.ibm.com \ --subject='Re: rcu_bh stalls on 3.2.28' \ /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
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).