Messages in this thread | | | From | Jose Abreu <> | Subject | RE: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool | Date | Mon, 22 Jul 2019 11:39:21 +0000 |
| |
From: Lars Persson <lists@bofh.nu> Date: Jul/22/2019, 12:11:50 (UTC+00:00)
> On Mon, Jul 22, 2019 at 12:18 PM Ilias Apalodimas > <ilias.apalodimas@linaro.org> wrote: > > > > On Thu, Jul 18, 2019 at 07:48:04AM +0000, Jose Abreu wrote: > > > From: Jon Hunter <jonathanh@nvidia.com> > > > Date: Jul/17/2019, 19:58:53 (UTC+00:00) > > > > > > > Let me know if you have any thoughts. > > > > > > Can you try attached patch ? > > > > > > > The log says someone calls panic() right? > > Can we trye and figure were that happens during the stmmac init phase? > > > > The reason for the panic is hidden in this one line of the kernel logs: > Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b > > The init process is killed by SIGSEGV (signal 11 = 0xb). > > I would suggest you look for data corruption bugs in the RX path. If > the code is fetched from the NFS mount then a corrupt RX buffer can > trigger a crash in userspace. > > /Lars
Jon, I'm not familiar with ARM. Are the buffer addresses being allocated in a coherent region ? Can you try attached patch which adds full memory barrier before the sync ?
--- Thanks, Jose Miguel Abreu [unhandled content-type:application/octet-stream] | |