Hi,
Yesterday i was doing some experiments with Kernel 5.3.0-rc4 on my NanoPi A64 and it was all looking good until i hit this error below.
I just let Kodi running in idle mode, turned off the monitor and the next day no HDMI output but the board was still running, i could ssh to it as usual.
I have no idea what to look for to find the reason or fix this problem.
Can this be a missing kernel configuration or a bug?
Can someone give some hints to fix the problem?
Here is the kernel message:
[67634.474921] bad: scheduling from the idle thread!
[67634.479649] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G WC O 5.3.0-rc4 #1
[67634.479655] Hardware name: FriendlyARM NanoPi A64 (DT)
[67634.479660] Call trace:
[67634.479673] dump_backtrace+0x0/0x150
[67634.479685] show_stack+0x14/0x20
[67634.479694] dump_stack+0xa8/0xcc
[67634.479705] dequeue_task_idle+0x24/0x38
[67634.479717] deactivate_task+0x70/0xc8
[67634.479728] __schedule+0x290/0x470
[67634.479739] schedule_idle+0x1c/0x38
[67634.479749] do_idle+0x194/0x2c0
[67634.479759] cpu_startup_entry+0x20/0x28
[67634.479770] secondary_start_kernel+0x1a0/0x1e0
[67634.481898] bad: scheduling from the idle thread!
[67634.487456] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G WC O 5.3.0-rc4 #1
[67634.487706] Hardware name: FriendlyARM NanoPi A64 (DT)
[67634.487797] Call trace:
[67634.488069] dump_backtrace+0x0/0x150
[67634.488316] show_stack+0x14/0x20
[67634.488502] dump_stack+0xa8/0xcc
[67634.488704] dequeue_task_idle+0x24/0x38
[67634.488944] deactivate_task+0x70/0xc8
[67634.489174] __schedule+0x290/0x470
[67634.489400] schedule_idle+0x1c/0x38
[67634.489592] do_idle+0x194/0x2c0
[67634.489788] cpu_startup_entry+0x20/0x28
[67634.490014] secondary_start_kernel+0x1a0/0x1e0
[67634.491423] bad: scheduling from the idle thread!
[67634.496843] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G WC O 5.3.0-rc4 #1
[67634.496960] Hardware name: FriendlyARM NanoPi A64 (DT)
[67634.497180] Call trace:
[67634.497446] dump_backtrace+0x0/0x150
[67634.497683] show_stack+0x14/0x20
[67634.497868] dump_stack+0xa8/0xcc
[67634.498069] dequeue_task_idle+0x24/0x38
[67634.498304] deactivate_task+0x70/0xc8
[67634.498533] __schedule+0x290/0x470
[67634.498757] schedule_idle+0x1c/0x38
[67634.498953] do_idle+0x194/0x2c0
[67634.499146] cpu_startup_entry+0x20/0x28
[67634.499371] secondary_start_kernel+0x1a0/0x1e0
[67634.614312] bad: scheduling from the idle thread!
Regards,
@lex