This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hello TI Experts.
We are using the TDA4AL platform, version sdk0806.
We are currently doing power-on and power-off stress testing. In the tens of thousands of tests on multiple boards, we found that some boards have the following errors with probability. idc_iuni.bin is an application we developed. Sometimes it is printed that it is caused by other applications, such as idc_vial.bin. Temporarily infer that it has nothing to do with our own application, because the entire kernel is dead, and it seems that it is not caused by the upper-level process. So I would like to ask what exactly causes such problems and how to solve them.
[ 4.354984] SError Interrupt on CPU0, code 0xbf000002 -- SError [ 4.354986] CPU: 0 PID: 382 Comm: idc_iuni.bin Not tainted 5.10.162-imotion 1 [ 4.354987] Hardware name: Texas Instruments J721S2 EVM (DT) [ 4.354988] pstate: 40000085 (nZcv daIf -PAN -UAO -TCO BTYPE=--) [ 4.354989] pc : _raw_spin_unlock+0x38/0x48 [ 4.354990] lr : handle_irq_event+0x40/0xe0 [ 4.354992] sp : ffff8000100031d0 [ 4.354993] x29: ffff8000100031d0 x28: ffff00083164cf80 [ 4.354997] x27: ffff800010a93480 x26: ffff00082e700f28 [ 4.354999] x25: ffff00082d547080 x24: ffff00082d724660 [ 4.355002] x23: ffff00083164cf80 x22: ffff00082d724600 [ 4.355004] x21: ffff00082d5c4cdc x20: ffff00082d5c4cdc [ 4.355006] x19: ffff00082d5c4c00 x18: 0000000000000000 [ 4.355009] x17: 0000000000000000 x16: 0000000000000000 [ 4.355011] x15: 0000000000000001 x14: ffff800010003850 [ 4.355013] x13: 00000000c0a80162 x12: 0000000000000000 [ 4.355016] x11: 0000000000000040 x10: ffff800010a5dd10 [ 4.355018] x9 : ffff800010a5dd08 x8 : ffff00082c4c6dd8 [ 4.355021] x7 : 0000000000000000 x6 : 0000000000000000 [ 4.355023] x5 : ffff80086f0a3000 x4 : ffff800010003200 [ 4.355025] x3 : ffff80086f0a3000 x2 : ffff00082d5c4c00 [ 4.355027] x1 : ffff00083164cf80 x0 : 0000000100010700 [ 4.355030] Kernel panic - not syncing: Asynchronous SError Interrupt [ 4.355054] SMP: stopping secondary CPUs [ 4.355055] Kernel Offset: 0x80000 from 0xffff800010000000 [ 4.355056] PHYS_OFFSET: 0x80000000 [ 4.355057] CPU features: 0x28040022,20806008 [ 4.355059] Memory Limit: none
Hi,
Tough to comment what exactly is going wrong here. Are there more logs?
Some hypothesis in the upstream Linux mailing lists: https://lore.kernel.org/linux-arm-kernel/b28b1585-742c-16be-3295-f00d03897579@arm.com/T/
That said cannot isolate much from the above logs.
- Keerthy