From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
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, 03 Sep 2012 14:05:11 +0800 [thread overview]
Message-ID: <50444897.6070803@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120831230256.GA7016@khazad-dum.debian.net>
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?
BTW:
Is this stall info comes from a virtual machine?
Regards,
Michael Wang
>
> There are previous reports of these weird rcu_bh stalls with t=0 in the 3.2
> and 3.3 branches as well:
>
> https://lkml.org/lkml/2012/2/18/34
> http://lkml.org/lkml/2012/3/28/175
>
> another data point:
> https://bugzilla.redhat.com/show_bug.cgi?id=806610
>
next prev parent reply other threads:[~2012-09-03 6:05 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 [this message]
2012-09-03 17:24 ` Henrique de Moraes Holschuh
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=50444897.6070803@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=ben@decadent.org.uk \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.