AnsweredAssumed Answered

S32V234 seq.ko issue

Question asked by Jinlong Bai on Aug 11, 2018
Latest reply on Aug 22, 2018 by Jinlong Bai

We designed a customer development board with reference to s32v234-evb28899. After DDR calibration and stress testing, we updated the contents of lpddr2.h and the board worked fine.

But after installing the seq.ko driver module, the kernel will report an error:

root@s32v234evb:~# insmod /s32v234/seq.ko
[ 29.232533] SEQ: driver ready.
[ 29.235514] Bad mode in Error handler detected, code 0xbf000002 -- SError
[ 29.242949] CPU: 3 PID: 911 Comm: insmod Tainted: G O 4.1.26-rt29+gbda2b35 #1
[ 29.252003] Hardware name: Freescale S32V234 (DT)
[ 29.257155] task: ffffffc044f44300 ti: ffffffc044a7c000 task.ti: ffffffc044a7c000
[ 29.265356] PC is at 0x7f9b2e85f4
[ 29.268978] LR is at 0x4100a4
[ 29.272222] pc : [<0000007f9b2e85f4>] lr : [<00000000004100a4>] pstate: 80000000
[ 29.280327] sp : ffffffc044a7fff0
[ 29.283952] x29: 0000007fe51578b0 x28: 0000000000000000
[ 29.289769] x27: 0000000000000000 x26: 0000000000000000
[ 29.295586] x25: 0000000000000000 x24: 0000007fe5157efb
[ 29.301404] x23: 0000007fe5157a98 x22: 0000000000000000
[ 29.307221] x21: 0000000000000000 x20: 000000000041a020
[ 29.313039] x19: 000000002398c090 x18: 0000000000000000
[ 29.318856] x17: 000000000042b600 x16: 0000007f9b2e85d0
[ 29.324674] x15: 0000007f9b3ba030 x14: 0000007f9b228664
[ 29.330492] x13: ffffffffffff0000 x12: 0000000000000000
[ 29.336309] x11: 0000000000000004 x10: 0101010101010101
[ 29.342127] x9 : 0000000000000003 x8 : 0000000000000111
[ 29.347944] x7 : ffffffffffffffff x6 : ffffffffffffffff
[ 29.353762] x5 : 60ceffffffffffff x4 : 0000000000000000
[ 29.359579] x3 : 0000000000000003 x2 : 0000000000000000
[ 29.365397] x1 : 000000000041a020 x0 : 0000000000000000
[ 29.371214]
[ 29.372849] Bad mode in Synchronous Abort handler detected, code 0x8600000f -- IABT (current EL)
[ 29.382471] CPU: 3 PID: 911 Comm: insmod Tainted: G O 4.1.26-rt29+gbda2b35 #1
[ 29.391528] Hardware name: Freescale S32V234 (DT)
[ 29.396680] task: ffffffc044f44300 ti: ffffffc044a7c000 task.ti: ffffffc044a7c000
[ 29.404881] PC is at 0x4100a4
[ 29.408123] LR is at 0x4100a4
[ 29.411366] pc : [<00000000004100a4>] lr : [<00000000004100a4>] pstate: 600003c5
[ 29.419472] sp : ffffffc044a7fed0
[ 29.423096] x29: 0000007fe51578b0 x28: 0000000000000000
[ 29.428913] x27: 0000000000000000 x26: 0000000000000000
[ 29.434731] x25: 0000000000000000 x24: 0000007fe5157efb
[ 29.440549] x23: 0000000080000000 x22: 0000007f9b2e85f4
[ 29.446366] x21: ffffffc044a7fff0 x20: 000000000041a020
[ 29.452184] x19: 000000002398c090 x18: 0000000000000000
[ 29.458001] x17: 000000000042b600 x16: 0000007f9b2e85d0
[ 29.463819] x15: 0000007f9b3ba030 x14: 3030303030303038
[ 29.469636] x13: 203a657461747370 x12: 205d3e3461303031
[ 29.475454] x11: ffffffc044a7fb50 x10: ffffffc044a7fb50
[ 29.481272] x9 : ffffffc0449f3000 x8 : 0000000000000010
[ 29.487089] x7 : 0000000000000010 x6 : ffffffc044a7fc20
[ 29.492907] x5 : 0000000000000003 x4 : 0000000000000000
[ 29.498724] x3 : 0000000000000003 x2 : 0000000000000036
[ 29.504542] x1 : ffffffc044a7c000 x0 : 0000000000000000


What caused this error?
How can I handle this error?
Or what hardware problems do we have to troubleshoot?

 

CPU:S32V234

LPDDR2: IS46LD32640B-18BLA2  x 2

KERNEL:4.1.26

U-BOOT:U-Boot 2016.01

YOCTO:auto_yocto_bsp  alb/master 

BSP:V16.1

BOOT FROM: SD

Attachments

Outcomes