From mboxrd@z Thu Jan 1 00:00:00 1970 From: Logan Gunthorpe Subject: Re: [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Date: Tue, 3 Jul 2018 17:20:34 -0600 Message-ID: References: <20180622194752.11221-1-logang@deltatee.com> <20180622194752.11221-7-logang@deltatee.com> <13ea3f97-4a33-3a24-1b7e-b819be73d867@deltatee.com> <6e5224b9-343f-990c-19bd-fe37c6fbdc9b@deltatee.com> <7ddda181-6337-32cc-7a0d-43fc6a7ba78b@deltatee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Andy Shevchenko Cc: Fabio Estevam , Andrew Morton , linux-kernel , Linux-Arch , linux-ntb@googlegroups.com, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Arnd Bergmann , Greg Kroah-Hartman , =?UTF-8?Q?Horia_Geant=c4=83?= , Dan Douglass , Herbert Xu , "David S. Miller" List-Id: linux-arch.vger.kernel.org On 03/07/18 04:21 PM, Andy Shevchenko wrote: > On Wed, Jul 4, 2018 at 12:20 AM, Logan Gunthorpe 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ale.deltatee.com ([207.54.116.67]:37684 "EHLO ale.deltatee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbeGCXUq (ORCPT ); Tue, 3 Jul 2018 19:20:46 -0400 References: <20180622194752.11221-1-logang@deltatee.com> <20180622194752.11221-7-logang@deltatee.com> <13ea3f97-4a33-3a24-1b7e-b819be73d867@deltatee.com> <6e5224b9-343f-990c-19bd-fe37c6fbdc9b@deltatee.com> <7ddda181-6337-32cc-7a0d-43fc6a7ba78b@deltatee.com> From: Logan Gunthorpe Message-ID: Date: Tue, 3 Jul 2018 17:20:34 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andy Shevchenko Cc: Fabio Estevam , Andrew Morton , linux-kernel , Linux-Arch , linux-ntb@googlegroups.com, "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Arnd Bergmann , Greg Kroah-Hartman , =?UTF-8?Q?Horia_Geant=c4=83?= , Dan Douglass , Herbert Xu , "David S. Miller" Message-ID: <20180703232034.Hvl7ebAwWtPLTWB_jbTVMGbLgEVWMTZu2zXbSb4MaRg@z> On 03/07/18 04:21 PM, Andy Shevchenko wrote: > On Wed, Jul 4, 2018 at 12:20 AM, Logan Gunthorpe 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