Re: arm64: unhandled level 0 translation fault

On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote: > Hi Dave, > > On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: > > On Thu, Dec 14, 2017 at 07:08:27PM +0100, Geert Uytterhoeven wrote: > >> On Thu, Dec 14, 2017 at 4:24 PM, Dave P Martin

Re: arm64: unhandled level 0 translation fault

On Fri, Dec 15, 2017 at 04:59:28PM +0100, Geert Uytterhoeven wrote: > On Fri, Dec 15, 2017 at 3:27 PM, Will Deacon wrote: > > On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote: > >> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: >

Re: arm64: unhandled level 0 translation fault

Hi Will, On Fri, Dec 15, 2017 at 3:27 PM, Will Deacon wrote: > On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote: >> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: >> > The two important differences here seem to be >> > >> > 1)

Re: arm64: unhandled level 0 translation fault

On Fri, Dec 15, 2017 at 3:27 PM, Will Deacon wrote: > On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote: >> On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: >> > The two important differences here seem to be >> > >> > 1) Staging the

Re: arm64: unhandled level 0 translation fault

On Fri, Dec 15, 2017 at 02:30:00PM +0100, Geert Uytterhoeven wrote: > On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: > > The two important differences here seem to be > > > > 1) Staging the state via current->thread.fpsimd_state instead of loading > > directly: > > > >

Re: arm64: unhandled level 0 translation fault

Hi Dave, On Fri, Dec 15, 2017 at 12:23 PM, Dave Martin wrote: > On Thu, Dec 14, 2017 at 07:08:27PM +0100, Geert Uytterhoeven wrote: >> On Thu, Dec 14, 2017 at 4:24 PM, Dave P Martin wrote: >> > On Thu, Dec 14, 2017 at 02:34:50PM +, Geert

Re: arm64: unhandled level 0 translation fault

On Thu, Dec 14, 2017 at 07:08:27PM +0100, Geert Uytterhoeven wrote: > Hi Dave, > > On Thu, Dec 14, 2017 at 4:24 PM, Dave P Martin wrote: > > On Thu, Dec 14, 2017 at 02:34:50PM +, Geert Uytterhoeven wrote: > >> On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven > >>

Re: arm64: unhandled level 0 translation fault

Hi Dave, On Thu, Dec 14, 2017 at 4:24 PM, Dave P Martin wrote: > On Thu, Dec 14, 2017 at 02:34:50PM +, Geert Uytterhoeven wrote: >> On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven >> wrote: >> > During userspace (Debian jessie NFS root) boot

Re: arm64: unhandled level 0 translation fault

On Thu, Dec 14, 2017 at 02:34:50PM +, Geert Uytterhoeven wrote: > Hi Catalin, Will, Dave, > > On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven > wrote: > > During userspace (Debian jessie NFS root) boot on arm64: > > > > rpcbind[1083]: unhandled level 0 translation

Re: arm64: unhandled level 0 translation fault

Hi Geert, On Thu, Dec 14, 2017 at 03:34:50PM +0100, Geert Uytterhoeven wrote: > On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven > wrote: > > During userspace (Debian jessie NFS root) boot on arm64: > > > > rpcbind[1083]: unhandled level 0 translation fault (11) at

Re: arm64: unhandled level 0 translation fault

Hi Catalin, Will, Dave, On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven wrote: > During userspace (Debian jessie NFS root) boot on arm64: > > rpcbind[1083]: unhandled level 0 translation fault (11) at 0x0008, > esr 0x9204, in dash[adf77000+1a000] > CPU: 0

Re: arm64: unhandled level 0 translation fault

Hi Geert, Thanks for trying to bisect this. On Tue, Dec 12, 2017 at 09:54:05PM +0100, Geert Uytterhoeven wrote: > On Tue, Dec 12, 2017 at 5:57 PM, Will Deacon wrote: > > Do you reckon you can bisect between -rc1 and -rc2? We've been unable to > > reproduce this on any of

Re: arm64: unhandled level 0 translation fault

Hi Will, On Tue, Dec 12, 2017 at 5:57 PM, Will Deacon wrote: > On Tue, Dec 12, 2017 at 05:00:33PM +0100, Geert Uytterhoeven wrote: >> On Tue, Dec 12, 2017 at 4:11 PM, Geert Uytterhoeven >> wrote: >> > On Tue, Dec 12, 2017 at 11:36 AM, Will Deacon

Re: arm64: unhandled level 0 translation fault

On Tue, Dec 12, 2017 at 05:00:33PM +0100, Geert Uytterhoeven wrote: > On Tue, Dec 12, 2017 at 4:11 PM, Geert Uytterhoeven > wrote: > > On Tue, Dec 12, 2017 at 11:36 AM, Will Deacon wrote: > >> On Tue, Dec 12, 2017 at 11:20:09AM +0100, Geert Uytterhoeven

Re: arm64: unhandled level 0 translation fault

Hi Will, On Tue, Dec 12, 2017 at 4:11 PM, Geert Uytterhoeven wrote: > On Tue, Dec 12, 2017 at 11:36 AM, Will Deacon wrote: >> On Tue, Dec 12, 2017 at 11:20:09AM +0100, Geert Uytterhoeven wrote: >>> During userspace (Debian jessie NFS root) boot on

Re: arm64: unhandled level 0 translation fault

Hi Will, On Tue, Dec 12, 2017 at 11:36 AM, Will Deacon wrote: > On Tue, Dec 12, 2017 at 11:20:09AM +0100, Geert Uytterhoeven wrote: >> During userspace (Debian jessie NFS root) boot on arm64: >> >> rpcbind[1083]: unhandled level 0 translation fault (11) at 0x0008, >> esr

Re: arm64: unhandled level 0 translation fault

Hi Geert, On Tue, Dec 12, 2017 at 11:20:09AM +0100, Geert Uytterhoeven wrote: > During userspace (Debian jessie NFS root) boot on arm64: > > rpcbind[1083]: unhandled level 0 translation fault (11) at 0x0008, > esr 0x9204, in dash[adf77000+1a000] > CPU: 0 PID: 1083 Comm: rpcbind Not

arm64: unhandled level 0 translation fault

Hi Catalin, Will, et al, During userspace (Debian jessie NFS root) boot on arm64: rpcbind[1083]: unhandled level 0 translation fault (11) at 0x0008, esr 0x9204, in dash[adf77000+1a000] CPU: 0 PID: 1083 Comm: rpcbind Not tainted 4.15.0-rc3-arm64-renesas-02176-g14f9a1826e48e355 #51