Re: NFS crash, hashed pointers in backtrace

On Wed, Dec 6, 2017 at 5:19 PM, Geert Uytterhoeven wrote: > On Wed, Dec 6, 2017 at 5:10 PM, Trond Myklebust > wrote: >> On Wed, 2017-12-06 at 15:31 +0100, Geert Uytterhoeven wrote: >>> On Tue, Dec 5, 2017 at 5:02 PM, Geert Uytterhoeven

Re: NFS crash, hashed pointers in backtrace

Hi Trond, On Wed, Dec 6, 2017 at 5:10 PM, Trond Myklebust wrote: > On Wed, 2017-12-06 at 15:31 +0100, Geert Uytterhoeven wrote: >> On Tue, Dec 5, 2017 at 5:02 PM, Geert Uytterhoeven > org> wrote: >> Got another nfsroot crash: >> >> Unable to handle

Re: NFS crash, hashed pointers in backtrace

Hi Geert, On Wed, 2017-12-06 at 15:31 +0100, Geert Uytterhoeven wrote: > Hi Trond. Anna, > > On Tue, Dec 5, 2017 at 5:02 PM, Geert Uytterhoeven org> wrote: > > During a failed write to a virtual sysfs file (root fs is NFS), I > > got: > > > > Unable to handle kernel NULL

Re: NFS crash, hashed pointers in backtrace

Hi Trond. Anna, On Tue, Dec 5, 2017 at 5:02 PM, Geert Uytterhoeven wrote: > During a failed write to a virtual sysfs file (root fs is NFS), I got: > > Unable to handle kernel NULL pointer dereference at virtual address 0020 > pgd = c448bb15 > [0020] *pgd=69c9c003,

Re: NFS crash, hashed pointers in backtrace

On Tue, Dec 5, 2017 at 8:02 AM, Geert Uytterhoeven wrote: > During a failed write to a virtual sysfs file (root fs is NFS), I got: > > Unable to handle kernel NULL pointer dereference at virtual address 0020 > pgd = c448bb15 Ok, this pgd value looks hashed, and should

NFS crash, hashed pointers in backtrace

During a failed write to a virtual sysfs file (root fs is NFS), I got: Unable to handle kernel NULL pointer dereference at virtual address 0020 pgd = c448bb15 [0020] *pgd=69c9c003, *pmd=69d55003, *pte= Internal error: Oops: 207 [#1] SMP ARM Modules linked in: CPU: 0 PID: 1230