linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rcu_bh stalls on 3.2.28
Date: Sun, 09 Sep 2012 19:12:07 +0100	[thread overview]
Message-ID: <1347214327.7709.55.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20120831230256.GA7016@khazad-dum.debian.net>

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

Please note that I can only directly deal with regressions that are
specific to 3.2, caused by a bad backport.  For anything else, you need
to identify an upstream fix to be applied - I'm not usually going to
have the time to do that.

On Fri, 2012-08-31 at 20:02 -0300, 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
> 
> 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

Says it was fixed in (Fedora's) 3.3 - so perhaps there are multiple bugs
involved.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      parent reply	other threads:[~2012-09-09 18:12 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
2012-09-09 18:12   ` Ben Hutchings [this message]

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=1347214327.7709.55.camel@deadeye.wl.decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --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).