Re: 4.9.30 NULL pointer dereference in __remove_shared_vm_struct

2017-06-08 Thread Tetsuo Handa
Tommi Rantala wrote: > I have hit this kernel bug twice with 4.9.30 while running trinity, any > ideas? It's not easily reproducible. No idea. But if you can reproduce this problem, I think you can retry with the OOM reaper disabled (like shown below), for the latter report is 10 seconds after

Re: 4.9.30 NULL pointer dereference in __remove_shared_vm_struct

2017-06-08 Thread Tetsuo Handa
Tommi Rantala wrote: > I have hit this kernel bug twice with 4.9.30 while running trinity, any > ideas? It's not easily reproducible. No idea. But if you can reproduce this problem, I think you can retry with the OOM reaper disabled (like shown below), for the latter report is 10 seconds after

4.9.30 NULL pointer dereference in __remove_shared_vm_struct

2017-06-07 Thread Tommi Rantala
Hi, I have hit this kernel bug twice with 4.9.30 while running trinity, any ideas? It's not easily reproducible. Perhaps I should enable some more debug options to see if they reveal anything... (note that I had different kernel builds, so the IP addresses are different in the logs below)

4.9.30 NULL pointer dereference in __remove_shared_vm_struct

2017-06-07 Thread Tommi Rantala
Hi, I have hit this kernel bug twice with 4.9.30 while running trinity, any ideas? It's not easily reproducible. Perhaps I should enable some more debug options to see if they reveal anything... (note that I had different kernel builds, so the IP addresses are different in the logs below)