mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	kernel test robot <oliver.sang@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org, lkp@intel.com, zhengjun.xing@linux.intel.com
Subject: Re: [printk]  b031a684bf: INFO:rcu_tasks_detected_stalls_on_tasks
Date: Thu, 28 Jan 2021 15:51:50 +0100	[thread overview]
Message-ID: <YBLPhkHQ8cXFiY1X@alley> (raw)
In-Reply-To: <87czxpmhe1.fsf@jogness.linutronix.de>

On Thu 2021-01-28 12:32:46, John Ogness wrote:
> On 2021-01-28, Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> >> # modprobe rcutorture onoff_interval=3 onoff_holdoff=30 torture_type=tasks
> >> 
> >> (Those are the same modprobe parameters used by the lkp job.)
> >> 
> >> After about a minute I see:
> >> 
> >> [   47.268292] tasks-torture: rcu_torture_read_exit: Start of episode
> >> [   51.273365] tasks-torture: rcu_torture_read_exit: End of episode
> >> [   55.823306] smpboot: do_boot_cpu failed(-1) to wakeup CPU#0
> >> [   55.824350] tasks-torture:torture_onoff task: online 0 failed: errno -5
> >> [   55.830661] tasks-torture:torture_onoff task: online 0 failed: errno -5
> >> [   55.848524] tasks-torture:torture_onoff task: online 0 failed: errno -5
> >
> > Just out of curious, this is seen only with the printk commit in
> > question applied?
> 
> No. The error messages are not related to the commit. But they are
> really the only thing printk'ing when the rcu stall happens. So you
> probably do need to see them in order to reproduce this. (Assuming this
> is somehow printk related.)

If you are able to reproduce this, it might be interesting to see
backtraces from all CPUs when RCU stall gets detected. Or even printing
all processes, even the sleeping ones.

I am still curious how this could be printk() related.

Best Regards,
Petr

  reply	other threads:[~2021-01-28 14:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  8:13 kernel test robot
2021-01-22 16:21 ` Petr Mladek
2021-01-26  4:52   ` Sergey Senozhatsky
2021-01-27 21:22     ` John Ogness
2021-01-27 23:29       ` John Ogness
2021-01-28  8:30       ` Sergey Senozhatsky
2021-01-28 11:26         ` John Ogness
2021-01-28 14:51           ` Petr Mladek [this message]
2021-01-28 15:42             ` John Ogness
2021-01-28 16:36               ` Petr Mladek
2021-01-28 17:36                 ` John Ogness
2021-01-28 21:38                   ` John Ogness
2021-01-23  2:44 ` Sergey Senozhatsky
2021-02-02 17:13 ` John Ogness
2021-02-04 21:32   ` John Ogness
2021-02-05  9:32     ` Petr Mladek

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=YBLPhkHQ8cXFiY1X@alley \
    --to=pmladek@suse.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=zhengjun.xing@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®