We can put aside Java Memory Leak. I downgraded to kernel 3.10.0-957.27.2.el7.x86_64, there are no more crashes.
The bug comes from ‘futex‘ syscall. What can causes that bug and how can i investigate ? Christophe Dumont Ligne directe : 0476842574 De : Valdis Kletnieks <val...@vt.edu> De la part de Valdis Kletnieks Envoyé : mercredi 16 octobre 2019 16:17 À : Christophe DUMONT <christophe.dum...@yoni.fr> Cc : kernelnewbies@kernelnewbies.org Objet : Re: Kernel Panic On Wed, 16 Oct 2019 07:34:01 -0000, Christophe DUMONT said: > What made me think about a memory leak is the message : Java Not Tainted > 3.10.0-1062.1.1.el7.x86_64.=20 That just tells you that the currently executing process was java. It says nothing at all about a memory leak, and as I already mentioned, if Java was leaking memory, it would almost certainly have been leaking memory on a previous kernel. The important part almost always isn't the running process, it's the kernel stack traceback, which in this case has 'futex' scribbled *all* over it. General rule of thumb: If you get more than one crash that has a similar traceback that points at a specific syscall, or file system driver, etc, the bug is almost guaranteed to be in that code. If you get a rash of crashes with *different* tracebacks, you probably have some other code that's overlaying memory.
pgpChrU4nARnk.pgp
Description: PGP signature
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
