public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Maxim Wexler <maxim.wexler@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] unstoppable, undeciperable kernel call trace in log
Date: Sat, 30 Jun 2012 21:11:13 -0600	[thread overview]
Message-ID: <CAN_TFxMnnWuGd6QaaPf5yxGUc=eE4xsg6QqFsUpxbszedR4ECA@mail.gmail.com> (raw)
In-Reply-To: <CAEH5T2PMed-EM6czgzgYeh_FPX-BO2wOf9OSv5qL3We582N=cQ@mail.gmail.com>

> Hi,
>
> I don't have an answer, but if you google the phrase "rcu_bh detected
> stall on CPU" you can find many reports similar to yours and maybe
> some information.

This might be usefu
lhttp://www.kernel.org/doc/Documentation/RCU/stallwarn.txt

"RCU bugs can often be debugged with the help of CONFIG_RCU_TRACE"

from <help> in menuconfig.

  │ This option provides tracing in RCU which presents stats                │
  │ in debugfs for debugging RCU implementation.

Ok, so I've  set the RCU_TRACE=y. Next question: How do I use debugfs,
never used it before?

>
> Do you have RCU_CPU_STALL_INFO=y in your kernel config?

no.

syzygy@lumby ~ $ grep RCU /usr/src/linux/.config
# RCU Subsystem
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_SPARSE_RCU_POINTER is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60



  reply	other threads:[~2012-07-01  3:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-30 21:57 [gentoo-user] unstoppable, undeciperable kernel call trace in log Maxim Wexler
2012-07-01  1:25 ` Paul Hartman
2012-07-01  3:11   ` Maxim Wexler [this message]
2012-07-01  3:46     ` Maxim Wexler

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='CAN_TFxMnnWuGd6QaaPf5yxGUc=eE4xsg6QqFsUpxbszedR4ECA@mail.gmail.com' \
    --to=maxim.wexler@gmail.com \
    --cc=gentoo-user@lists.gentoo.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