Skip to content

Conversation

@pjdobrowolski
Copy link
Contributor

Update zephyr main to support PTL target

Copy link
Collaborator

@kv2019i kv2019i left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw, not sure what is missing. This PR is mostly pulling minor fixes not affecting SOF. There is one PTL SOF fix, so maybe that's why you need this:
e452bc36a6d9e4544b07e24efe81e64c7178ad93 dai: ssp/ptl: Add missing definition in PTL

Update zephyr main to support PTL target for dai/ssp

e452bc36a6d9 dai: ssp/ptl: Add missing definition in PTL

Signed-off-by: Dobrowolski, PawelX <pawelx.dobrowolski@intel.com>
@kv2019i
Copy link
Collaborator

kv2019i commented Jun 19, 2024

We have a Zephyr panic on Intel LNL with SSP:
https://sof-ci.01.org/sofpr/PR9241/build5778/devicetest/index.html?model=LNLM_RVP_NOCODEC&testcase=check-pause-resume-capture-100

[ 1113.471561]  dai_intel_ssp: dai_ssp_get_properties: SSP0: fifo 164112, handshake 1, init delay 0
[ 1113.471570]  dai_intel_ssp: dai_ssp_early_start: SSP0 RX
[ 1113.471576]  os: print_fatal_exception:  ** FATAL EXCEPTION
[ 1113.471583]  os: print_fatal_exception:  ** CPU 0 EXCCAUSE 13 (load/store PIF data error)
[ 1113.471586]  os: print_fatal_exception:  **  PC 0xa003ae6a VADDR 0x28108
[ 1113.471590]  os: print_fatal_exception:  **  PS 0x60720
[ 1113.471593]  os: print_fatal_exception:  **    (INTLEVEL:0 EXCM: 0 UM:1 RING:0 WOE:1 OWB:7 CALLINC:2)
[ 1113.471598]  os: xtensa_dump_stack:  **  A0 0xa006291e  SP 0xa00f53e0  A2 0x4010ce1c  A3 0x400f0c30
[ 1113.471601]  os: xtensa_dump_stack:  **  A4 0x60d20  A5 0x400f0c30  A6 0x28100  A7 0xa00f53e0
[ 1113.471605]  os: xtensa_dump_stack:  **  A8 0xa003ae60  A9 0xa00f5370 A10 0xa00ebf88 A11 0x20c0
[ 1113.471608]  os: xtensa_dump_stack:  ** A12 0xfff001ff A13 0x10 A14 0x4010a6a0 A15 0xa00f5370
[ 1113.471611]  os: xtensa_dump_stack:  ** LBEG 0xa0037305 LEND 0xa0037314 LCOUNT 0xa005fe47
[ 1113.471615]  os: xtensa_dump_stack:  ** SAR 0x3
[ 1113.471618]  os: xtensa_dump_stack:  **  THREADPTR (nil)

--
Backtrace:0xa003ae67:0xa00f53e0 0xa006291b:0xa00f5410 0xa0071cb2:0xa00f5460 0xa0071ada:0xa00f5490 0xa007aa05:0xa00f54c0 0xa007a0a3:0xa00f54e0 0xa00749d0:0xa00f5580 0xa004285d:0xa00f55a0 0xa00423a2:0xa00f55f0 0xa004294e:0xa00f5620 0xa00423a2:0xa00f5670 0xa004294e:0xa00f56a0 0xa006a868:0xa00f56f0 0xa006a521:0xa00f5760 0xa006a497:0xa00f5790 0xa003f3ee:0xa00f57d0 0xa00680c0:0xa00f5800 0xa006ac93:0xa00f5820 0xa005f567:0xa00f5870 

[ 1113.471753]  os: z_fatal_error: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[ 1113.471758]  os: z_fatal_error: Current thread: 0x4010d3b8 (unknown)
[ 1113.473448]  zephyr: k_sys_fatal_error_handler: Halting syste

@pjdobrowolski can you check? I don't think we have this with SOF baseline.

@kv2019i
Copy link
Collaborator

kv2019i commented Jun 20, 2024

@pjdobrowolski and others, the panic was caused by the previous Zephyr update, @dnikodem has already rootcaused and is working on a fix. Tracking at #9245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants