On 7/3/2018 1:40 PM, Fabio Estevam wrote: >> So I have no idea what's going on here... Are we sure this is the patch >> causing the problem? Did you bisect? > > Yes, I am sure that 46e4bf08f6388ba748 is the one causing the kernel boot issue. Also, it could be helpful if you can compile with CONFIG_DEBUG_INFO and use gdb to find out what line "caam_jr_interrupt+0x120" points to in your image. When I do it on my setup, it doesn't point to a sensible line possibly due to different compilers. Thanks, Logan
