[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c64cd9c9-3eb5-acbd-3578-b32ec39d3ea4@deltatee.com>
Date: Tue, 3 Jul 2018 17:20:34 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Fabio Estevam <festevam@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
linux-ntb@...glegroups.com,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Horia Geantă <horia.geanta@....com>,
Dan Douglass <dan.douglass@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when
using io{read|write}64
On 03/07/18 04:21 PM, Andy Shevchenko wrote:
> On Wed, Jul 4, 2018 at 12:20 AM, Logan Gunthorpe <logang@...tatee.com> 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
Powered by blists - more mailing lists