Further digging indicates the hang is related to -1 being passed to __log2() and the way this function is implemented (left shift and compare). However, I'm still curious about the jump address not being the start address of any instruction. Is this a feature of Xtensa architecture?

I'm looking into an issue where the system hangs and would trigger task watchdog if enabled. Backtrace reported by WDT looks like the following: backtrace.png Seems the hang happens inside a call to __log2(), which is itself a simple function: __uint32_t __log2(num) __uint32_t num; { __uint32_t i, l...