IMX6 linux3.14.52 INFO: rcu_preempt detected stalls on CPUs/tasks: { 0}

cancel
Showing results for 
Search instead for 
Did you mean: 

IMX6 linux3.14.52 INFO: rcu_preempt detected stalls on CPUs/tasks: { 0}

877 Views
864535720
Contributor II

Hello everyone, my chip model is IMX6D and the chip frequency is 1G HZ. We are designing with reference to the official website IMX6 development board. We are using a Linux system, the version is 3.14.52. During the use, we encountered the following problems:
INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=2102 jiffies, g=4294967246, c=4294967245, q=231)
Task dump for CPU 0:
imx6_y R running 0 458 1 0x00000002
[<80660550>] (__schedule) from [<80660b98>] (io_schedule+0x70/0x9c)
[<80660b98>] (io_schedule) from [<976b66f4>] (0x976b66f4)
INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=8407 jiffies, g=4294967246, c=4294967245, q=852)
Task dump for CPU 0:
imx6_y R running 0 458 1 0x00000002
[<80660550>] (__schedule) from [<80660b98>] (io_schedule+0x70/0x9c)
[<80660b98>] (io_schedule) from [<976b66f4>] (0x976b66f4)
INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=14712 jiffies, g=4294967246, c=4294967245, q=1483)
Task dump for CPU 0:
imx6_y R running 0 458 1 0x00000002
[<80660550>] (__schedule) from [<80660b98>] (io_schedule+0x70/0x9c)
[<80660b98>] (io_schedule) from [<976b66f4>] (0x976b66f4)

Looking forward to anyone’s help.

Labels (3)
0 Kudos
2 Replies

683 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi 其东 刘 

"rcu_preempt detected stalls" may relate to arm/gpu errata which were fixed

in later linux releases, so one can try latest linux described on:

i.MX Software | NXP 

make sure that "#define CONFIG_ARM_ERRATA_" included in uboot :

mx6_common.h\configs\include - uboot-imx - i.MX U-Boot 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

683 Views
864535720
Contributor II

hi,igorpadykov

My uboot is the same as what you provided. It defines "CONFIG_ARM_ERRATA_", so you can rule out the problem of uboot.
You said that this problem has been fixed in the high version. Can you add a patch to the 3.14.52 version to solve this problem? Because our previous functional and stability tests were based on 3.14.52.

0 Kudos