Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-14 Thread James Morse
Hi Marek, On 14/10/2019 10:02, Marek Szyprowski wrote: > On 11.10.2019 16:42, Sudeep Holla wrote: >> On Fri, Oct 11, 2019 at 02:43:54PM +0100, Sudeep Holla wrote: >>> On Fri, Oct 11, 2019 at 03:15:32PM +0200, Marek Szyprowski wrote: On 11.10.2019 15:10, Sudeep Holla wrote: > On Fri, Oct

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-14 Thread Marek Szyprowski
Hi Sudeep, On 11.10.2019 16:42, Sudeep Holla wrote: > On Fri, Oct 11, 2019 at 02:43:54PM +0100, Sudeep Holla wrote: >> On Fri, Oct 11, 2019 at 03:15:32PM +0200, Marek Szyprowski wrote: >>> Hi Sudeep >>> >>> On 11.10.2019 15:10, Sudeep Holla wrote: On Fri, Oct 11, 2019 at 03:02:42PM +0200,

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Sudeep Holla
On Fri, Oct 11, 2019 at 02:43:54PM +0100, Sudeep Holla wrote: > On Fri, Oct 11, 2019 at 03:15:32PM +0200, Marek Szyprowski wrote: > > Hi Sudeep > > > > On 11.10.2019 15:10, Sudeep Holla wrote: > > > On Fri, Oct 11, 2019 at 03:02:42PM +0200, Marek Szyprowski wrote: > > >> Hi James, > > >> > > >> On

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Sudeep Holla
On Fri, Oct 11, 2019 at 03:15:32PM +0200, Marek Szyprowski wrote: > Hi Sudeep > > On 11.10.2019 15:10, Sudeep Holla wrote: > > On Fri, Oct 11, 2019 at 03:02:42PM +0200, Marek Szyprowski wrote: > >> Hi James, > >> > >> On 11.10.2019 12:38, James Morse wrote: > >>> Hi guys, > >>> > >>> On 11/10/2019

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Marek Szyprowski
Hi Sudeep On 11.10.2019 15:10, Sudeep Holla wrote: > On Fri, Oct 11, 2019 at 03:02:42PM +0200, Marek Szyprowski wrote: >> Hi James, >> >> On 11.10.2019 12:38, James Morse wrote: >>> Hi guys, >>> >>> On 11/10/2019 11:05, Sudeep Holla wrote: On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Sudeep Holla
On Fri, Oct 11, 2019 at 03:02:42PM +0200, Marek Szyprowski wrote: > Hi James, > > On 11.10.2019 12:38, James Morse wrote: > > Hi guys, > > > > On 11/10/2019 11:05, Sudeep Holla wrote: > >> On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: > >>> Recently I've got access to ARM Juno

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Marek Szyprowski
Hi James, On 11.10.2019 12:38, James Morse wrote: > Hi guys, > > On 11/10/2019 11:05, Sudeep Holla wrote: >> On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: >>> Recently I've got access to ARM Juno R1 board and did some tests with >>> current mainline kernel on it. I'm a bit

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Sudeep Holla
On Fri, Oct 11, 2019 at 11:38:17AM +0100, James Morse wrote: > Hi guys, > > On 11/10/2019 11:05, Sudeep Holla wrote: > > On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: > >> Recently I've got access to ARM Juno R1 board and did some tests with > >> current mainline kernel on it.

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread James Morse
Hi guys, On 11/10/2019 11:05, Sudeep Holla wrote: > On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: >> Recently I've got access to ARM Juno R1 board and did some tests with >> current mainline kernel on it. I'm a bit surprised that enabling >> CONFIG_PROVE_LOCKING causes a boot

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Marek Szyprowski
Hi Sudeep, On 11.10.2019 12:05, Sudeep Holla wrote: > Hi Marek, > > On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: >> Hi >> >> Recently I've got access to ARM Juno R1 board and did some tests with >> current mainline kernel on it. I'm a bit surprised that enabling >>

Re: ARM Juno r1 + CONFIG_PROVE_LOCKING=y => boot failure

2019-10-11 Thread Sudeep Holla
Hi Marek, On Fri, Oct 11, 2019 at 11:26:04AM +0200, Marek Szyprowski wrote: > Hi > > Recently I've got access to ARM Juno R1 board and did some tests with > current mainline kernel on it. I'm a bit surprised that enabling > CONFIG_PROVE_LOCKING causes a boot failure on this board. After enabling