On 03/07/18 04:21 PM, Andy Shevchenko wrote: > On Wed, Jul 4, 2018 at 12:20 AM, Logan Gunthorpe <logang@xxxxxxxxxxxx> wrote: >> On 7/3/2018 1:40 PM, Fabio Estevam wrote: > >> 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. > > It is an explicit call to BUG(). > That's why we see wrong instruction trap. Oh. So some IO in some other place must have changed to trigger the BUG... Logan
