From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: weird RCU problem with 4.4.0
Date: Mon, 01 Feb 2016 17:19:16 +0100 [thread overview]
Message-ID: <87d1sgl7y3.fsf@gmail.com> (raw)
Hi,
in the dmesg log (actually "journalctl -f") of one of my machines I had this:
...
03:25:01 CRON[16607]: pam_unix(cron:session): session closed for user root
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=301
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=301
(detected by 0, t=303 jiffies, g=2533688, c=2533687, q=4860)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=1204
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=1205
(detected by 0, t=1208 jiffies, g=2533688, c=2533687, q=19822)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=2109
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=2109
(detected by 0, t=2113 jiffies, g=2533688, c=2533687, q=34248)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=3011
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=3011
(detected by 0, t=3018 jiffies, g=2533688, c=2533687, q=48662)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=3912
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=3912
(detected by 0, t=3923 jiffies, g=2533688, c=2533687, q=63080)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=4815
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=4815
(detected by 0, t=4828 jiffies, g=2533688, c=2533687, q=68037)
...
and so on, and so forth ...
...
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=137745
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=137746
(detected by 0, t=137863 jiffies, g=2533688, c=2533687, q=68849)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=138651
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=138652
WARNING: multiple messages have this Message-ID (diff)
From: Holger Schurig <holgerschurig@gmail.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: weird RCU problem with 4.4.0
Date: Mon, 01 Feb 2016 17:19:16 +0100 [thread overview]
Message-ID: <87d1sgl7y3.fsf@gmail.com> (raw)
Hi,
in the dmesg log (actually "journalctl -f") of one of my machines I had this:
...
03:25:01 CRON[16607]: pam_unix(cron:session): session closed for user root
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=301
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=301
(detected by 0, t=303 jiffies, g=2533688, c=2533687, q=4860)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=1204
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=1205
(detected by 0, t=1208 jiffies, g=2533688, c=2533687, q=19822)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=2109
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=2109
(detected by 0, t=2113 jiffies, g=2533688, c=2533687, q=34248)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=3011
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=3011
(detected by 0, t=3018 jiffies, g=2533688, c=2533687, q=48662)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=3912
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=3912
(detected by 0, t=3923 jiffies, g=2533688, c=2533687, q=63080)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=4815
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=4815
(detected by 0, t=4828 jiffies, g=2533688, c=2533687, q=68037)
...
and so on, and so forth ...
...
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=137745
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=137746
(detected by 0, t=137863 jiffies, g=2533688, c=2533687, q=68849)
INFO: rcu_preempt detected stalls on CPUs/tasks:
1-...: (1 GPs behind) idle=763/140000000000000/0 softirq=6109762/6109762 fqs=138651
2-...: (1 GPs behind) idle=2f3/140000000000000/0 softirq=5129036/5129037 fqs=138652
next reply other threads:[~2016-02-01 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 16:19 Holger Schurig [this message]
2016-02-01 16:19 ` weird RCU problem with 4.4.0 Holger Schurig
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=87d1sgl7y3.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 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.