From: Christophe DUMONT <Christophe.DUMONT@yoni.fr>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: RE: Kernel Panic
Date: Wed, 16 Oct 2019 07:34:01 +0000 [thread overview]
Message-ID: <6f0b5da167fd4605b5f3dbdb7dc809b0@SRV-EXCH-2K13.Groupe-Yoni.fr> (raw)
In-Reply-To: <95848.1571170801@turing-police>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1263 bytes --]
Hello,
What made me think about a memory leak is the message : Java Not Tainted 3.10.0-1062.1.1.el7.x86_64.
I can’t access the bug report referenced : an active redhat subscription is needed !
Christophe Dumont
Ligne directe : 0476842574
De : Valdis Kletnieks <valdis@vt.edu> De la part de Valdis Kletnieks
Envoyé : mardi 15 octobre 2019 22:20
À : Christophe DUMONT <Christophe.DUMONT@yoni.fr>
Cc : kernelnewbies@kernelnewbies.org
Objet : Re: Kernel Panic
On Tue, 15 Oct 2019 07:21:18 -0000, Christophe DUMONT said:
> We're facing Kernel Panic on CentOS 7 since upgrading from 3.10.0-957 to 3.10.0-1062. I'm thinking about a java memory leak, but not sure.
> Do you know what's going on here ?
Well, what made you think "Java memory leak"?
Java is userspace. If it's leaking memory so far that the kernel has problems, it would probably:
a) Have been leaking memory and causing problems in -957 as well
b) Died in the OOM (Out Of Memory) code, rather than in the futex() system call.
Yes, poorly written Java code will leak memory like a sieve, but this doesn't smell
anything remotely like a memory leak.
I agree with Valentin that it's probably the bug report he references.
[-- Attachment #1.1.1.2: Type: text/html, Size: 6329 bytes --]
[-- Attachment #1.1.2: image001.png --]
[-- Type: image/png, Size: 8367 bytes --]
[-- Attachment #1.2: Type: application/pgp-signature, Size: 489 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 7:35 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 [this message]
2019-10-16 14:16 ` Valdis Klētnieks
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=6f0b5da167fd4605b5f3dbdb7dc809b0@SRV-EXCH-2K13.Groupe-Yoni.fr \
--to=christophe.dumont@yoni.fr \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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).