Custom hardware based on RPI2
Os release: this issue has been observed starting the 2.27.0 release and moving forward up to 2.31.5, but it might also occur on older releases.
[ 1415.123616] rcu_sched kthread starved for 115580 jiffies! g4165 c4164 f0x2 RCU_GP_WAIT_FQS(3) ->state=0x2002
[ 1415.142177] rcu_sched R 0 8 2 0x00000000
[ 1415.155937] [<808740c4>] (__schedule) from [<80874814>] (schedule+0x4c/0xac)
[ 1415.171343] [<80874814>] (schedule) from [<80878638>] (schedule_timeout+0xa0/0x44c)
[ 1415.187350] [<80878638>] (schedule_timeout) from [<8018a00c>] (rcu_gp_kthread+0x4a0/0x8d0)
[ 1415.203930] [<8018a00c>] (rcu_gp_kthread) from [<8014002c>] (kthread+0x170/0x178)
[ 1415.219578] [<8014002c>] (kthread) from [<801087ac>] (ret_from_fork+0x14/0x28)
[ 1468.118014] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1468.131307] 0-...: (1 GPs behind) idle=af2/2/0 softirq=14519/14519 fqs=6
[ 1468.145980] (detected by 3, t=121897 jiffies, g=4165, c=4164, q=316)
[ 1468.160265] Sending NMI from CPU 3 to CPUs 0:
vicgal
commented
5 years ago
Custom hardware based on RPI2 Os release: this issue has been observed starting the 2.27.0 release and moving forward up to 2.31.5, but it might also occur on older releases.