From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Christophe DUMONT <Christophe.DUMONT@yoni.fr>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel Panic
Date: Wed, 16 Oct 2019 10:16:42 -0400 [thread overview]
Message-ID: <147490.1571235402@turing-police> (raw)
In-Reply-To: <6f0b5da167fd4605b5f3dbdb7dc809b0@SRV-EXCH-2K13.Groupe-Yoni.fr>
[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]
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.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-16 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 7:21 Kernel Panic Christophe DUMONT
2019-10-15 17:13 ` Valentin Vidić
2019-10-15 20:20 ` Valdis Klētnieks
2019-10-16 7:34 ` Christophe DUMONT
2019-10-16 14:16 ` Valdis Klētnieks [this message]
2019-10-17 7:48 ` Christophe DUMONT
2019-10-17 7:54 ` Valentin Vidić
2019-10-22 9:38 ` Christophe DUMONT
2019-10-22 17:20 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2015-10-15 11:23 kernel panic jinzhao at wingtech.com
2015-10-16 11:36 ` Mulyadi Santosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=147490.1571235402@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Christophe.DUMONT@yoni.fr \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).