Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
* Kernel Panic
@ 2019-10-15  7:21 Christophe DUMONT
  2019-10-15 17:13 ` Valentin Vidić
  2019-10-15 20:20 ` Valdis Klētnieks
  0 siblings, 2 replies; 11+ messages in thread
From: Christophe DUMONT @ 2019-10-15  7:21 UTC (permalink / raw)
  To: kernelnewbies

[-- Attachment #1.1.1: Type: text/plain, Size: 253 bytes --]

Hello Kernel World,

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 ?

Christophe

[cid:image001.png@01D58339.CD24E760]

[-- Attachment #1.1.2: Type: text/html, Size: 3284 bytes --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR">Hello Kernel World,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR">We&#8217;re facing Kernel Panic on CentOS 7 since upgrading from
<b>3.10.0-957</b> to <b>3.10.0-1062</b>. I&#8217;m thinking about a java memory leak, but not sure.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR">Do you know what&#8217;s going on here&nbsp;?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:FR">Christophe<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:FR"><img width="1199" height="666" style="width:12.4895in;height:6.9375in" id="Image_x0020_1" src="cid:image001.png@01D58339.CD24E760"></span><o:p></o:p></p>
</div>
</body>
</html>

[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 52202 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Kernel Panic
  2019-10-15  7:21 Kernel Panic Christophe DUMONT
@ 2019-10-15 17:13 ` Valentin Vidić
  2019-10-15 20:20 ` Valdis Klētnieks
  1 sibling, 0 replies; 11+ messages in thread
From: Valentin Vidić @ 2019-10-15 17:13 UTC (permalink / raw)
  To: kernelnewbies

On Tue, Oct 15, 2019 at 07:21:18AM +0000, Christophe DUMONT wrote:
> 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 ?

Looks similar to this: https://access.redhat.com/solutions/4164501

-- 
Valentin

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Kernel Panic
  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
  1 sibling, 1 reply; 11+ messages in thread
From: Valdis Klētnieks @ 2019-10-15 20:20 UTC (permalink / raw)
  To: Christophe DUMONT; +Cc: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]

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.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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* RE: Kernel Panic
  2019-10-15 20:20 ` Valdis Klētnieks
@ 2019-10-16  7:34   ` Christophe DUMONT
  2019-10-16 14:16     ` Valdis Klētnieks
  0 siblings, 1 reply; 11+ messages in thread
From: Christophe DUMONT @ 2019-10-16  7:34 UTC (permalink / raw)
  To: Valdis Klētnieks; +Cc: kernelnewbies

[-- 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 --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
p.kicker, li.kicker, div.kicker
	{mso-style-name:kicker;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Hello, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>What made me think about a memory leak is the message&nbsp;: <i>Java Not Tainted 3.10.0-1062.1.1.el7.x86_64.</i> <o:p></o:p></span></p><p class=kicker style='background:#F0F0F0'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>I can’t access the bug report referenced&nbsp;: an active redhat subscription is needed&nbsp;!</span><span style='font-family:"Helvetica",sans-serif;color:#252525'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Christophe Dumont<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Ligne directe&nbsp;: 0476842574<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'><img width=171 height=101 style='width:1.7812in;height:1.052in' id="Image_x0020_1" src="cid:image001.png@01D58404.42038440" alt="Description&nbsp;: Logo_Yoni_Groupe_small"></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>De&nbsp;:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Valdis Kletnieks &lt;valdis@vt.edu&gt; <b>De la part de</b> Valdis Kletnieks<br><b>Envoyé&nbsp;:</b> mardi 15 octobre 2019 22:20<br><b>À&nbsp;:</b> Christophe DUMONT &lt;Christophe.DUMONT@yoni.fr&gt;<br><b>Cc&nbsp;:</b> kernelnewbies@kernelnewbies.org<br><b>Objet&nbsp;:</b> Re: Kernel Panic<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p><span style='font-family:"Calibri",sans-serif'>On Tue, 15 Oct 2019 07:21:18 -0000, Christophe DUMONT said:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>&gt; 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.</span><o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>&gt; Do you know what's going on here ?</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Well, what made you think &quot;Java memory leak&quot;?</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Java is userspace.&nbsp; If it's leaking memory so far that the kernel has problems, it would probably:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>a) Have been leaking memory and causing problems in -957 as well</span> <br><span style='font-family:"Calibri",sans-serif'>b) Died in the OOM (Out Of Memory) code, rather than in the futex() system call.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Yes, poorly written Java code will leak memory like a sieve, but this doesn't smell</span> <br><span style='font-family:"Calibri",sans-serif'>anything remotely like a memory leak.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>I agree with Valentin that it's probably the bug report he references.</span> <o:p></o:p></p></div></body></html>

[-- 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Kernel Panic
  2019-10-16  7:34   ` Christophe DUMONT
@ 2019-10-16 14:16     ` Valdis Klētnieks
  2019-10-17  7:48       ` Christophe DUMONT
  2019-10-22  9:38       ` Christophe DUMONT
  0 siblings, 2 replies; 11+ messages in thread
From: Valdis Klētnieks @ 2019-10-16 14:16 UTC (permalink / raw)
  To: Christophe DUMONT; +Cc: kernelnewbies

[-- 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* RE: Kernel Panic
  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
  1 sibling, 1 reply; 11+ messages in thread
From: Christophe DUMONT @ 2019-10-17  7:48 UTC (permalink / raw)
  To: Valdis Klētnieks; +Cc: kernelnewbies

[-- Attachment #1.1.1.1: Type: text/plain, Size: 1436 bytes --]

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 <valdis@vt.edu> De la part de Valdis Kletnieks
Envoyé : mercredi 16 octobre 2019 16:17
À : Christophe DUMONT <Christophe.DUMONT@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. 

 

[-- Attachment #1.1.1.2: Type: text/html, Size: 6353 bytes --]


<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>We can put aside Java Memory Leak.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>I downgraded to kernel 3.10.0-957.27.2.el7.x86_64, there are no more crashes. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>The bug comes from ‘futex‘ syscall. What can causes that bug and how can i investigate&nbsp;?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Christophe Dumont<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Ligne directe&nbsp;: 0476842574<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'><img width=171 height=101 style='width:1.7812in;height:1.052in' id="Image_x0020_1" src="cid:image001.png@01D584CF.DC7C5490" alt="Description&nbsp;: Logo_Yoni_Groupe_small"></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>De&nbsp;:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Valdis Kletnieks &lt;valdis@vt.edu&gt; <b>De la part de</b> Valdis Kletnieks<br><b>Envoyé&nbsp;:</b> mercredi 16 octobre 2019 16:17<br><b>&Agrave;&nbsp;:</b> Christophe DUMONT &lt;Christophe.DUMONT@yoni.fr&gt;<br><b>Cc&nbsp;:</b> kernelnewbies@kernelnewbies.org<br><b>Objet&nbsp;:</b> Re: Kernel Panic<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p><span style='font-family:"Calibri",sans-serif'>On Wed, 16 Oct 2019 07:34:01 -0000, Christophe DUMONT said:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>&gt; What made me think about a memory leak is the message : Java Not Tainted 3.10.0-1062.1.1.el7.x86_64.=20</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>That just tells you that the currently executing process was java.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>It says nothing at all about a memory leak, and as I already mentioned, if Java</span> <br><span style='font-family:"Calibri",sans-serif'>was leaking memory, it would almost certainly have been leaking memory on a</span> <br><span style='font-family:"Calibri",sans-serif'>previous kernel.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>The important part almost always isn't the running process, it's the kernel</span> <br><span style='font-family:"Calibri",sans-serif'>stack traceback, which in this case has 'futex' scribbled *all* over it.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>General rule of thumb:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>If you get more than one crash that has a similar traceback that points at a</span> <br><span style='font-family:"Calibri",sans-serif'>specific syscall, or file system driver, etc, the bug is almost guaranteed to</span> <br><span style='font-family:"Calibri",sans-serif'>be in that code.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>If you get a rash of crashes with *different* tracebacks, you probably have</span> <br><span style='font-family:"Calibri",sans-serif'>some other code that's overlaying memory.</span> <o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

[-- 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Kernel Panic
  2019-10-17  7:48       ` Christophe DUMONT
@ 2019-10-17  7:54         ` Valentin Vidić
  0 siblings, 0 replies; 11+ messages in thread
From: Valentin Vidić @ 2019-10-17  7:54 UTC (permalink / raw)
  To: kernelnewbies

On Thu, Oct 17, 2019 at 07:48:49AM +0000, Christophe DUMONT wrote:
> 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 ?

You can try to get the source for these two versions and compare. If the
diff is not too big it might give you some idea what changed...

-- 
Valentin

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 11+ messages in thread

* RE: Kernel Panic
  2019-10-16 14:16     ` Valdis Klētnieks
  2019-10-17  7:48       ` Christophe DUMONT
@ 2019-10-22  9:38       ` Christophe DUMONT
  2019-10-22 17:20         ` Greg KH
  1 sibling, 1 reply; 11+ messages in thread
From: Christophe DUMONT @ 2019-10-22  9:38 UTC (permalink / raw)
  To: Valdis Klētnieks; +Cc: kernelnewbies

[-- Attachment #1.1.1.1: Type: text/plain, Size: 1332 bytes --]

Hello, 

 

We downgraded to older kernel. We still facing the same Kernel Panic with different Kernel. 

 

 

Christophe Dumont

Ligne directe : 0476842574



 

De : Valdis Kletnieks <valdis@vt.edu> De la part de Valdis Kletnieks
Envoyé : mercredi 16 octobre 2019 16:17
À : Christophe DUMONT <Christophe.DUMONT@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. 

 

[-- Attachment #1.1.1.2: Type: text/html, Size: 6241 bytes --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Hello, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>We downgraded to older kernel. We still facing the same Kernel Panic with different Kernel. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Christophe Dumont<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Ligne directe&nbsp;: 0476842574<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial",sans-serif;color:black'><img width=171 height=101 style='width:1.7812in;height:1.052in' id="Image_x0020_1" src="cid:image001.png@01D588CC.FC9B26B0" alt="Description&nbsp;: Logo_Yoni_Groupe_small"></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>De&nbsp;:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Valdis Kletnieks &lt;valdis@vt.edu&gt; <b>De la part de</b> Valdis Kletnieks<br><b>Envoyé&nbsp;:</b> mercredi 16 octobre 2019 16:17<br><b>À&nbsp;:</b> Christophe DUMONT &lt;Christophe.DUMONT@yoni.fr&gt;<br><b>Cc&nbsp;:</b> kernelnewbies@kernelnewbies.org<br><b>Objet&nbsp;:</b> Re: Kernel Panic<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p>&nbsp;</o:p></p><p><span style='font-family:"Calibri",sans-serif'>On Wed, 16 Oct 2019 07:34:01 -0000, Christophe DUMONT said:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>&gt; What made me think about a memory leak is the message : Java Not Tainted 3.10.0-1062.1.1.el7.x86_64.=20</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>That just tells you that the currently executing process was java.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>It says nothing at all about a memory leak, and as I already mentioned, if Java</span> <br><span style='font-family:"Calibri",sans-serif'>was leaking memory, it would almost certainly have been leaking memory on a</span> <br><span style='font-family:"Calibri",sans-serif'>previous kernel.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>The important part almost always isn't the running process, it's the kernel</span> <br><span style='font-family:"Calibri",sans-serif'>stack traceback, which in this case has 'futex' scribbled *all* over it.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>General rule of thumb:</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>If you get more than one crash that has a similar traceback that points at a</span> <br><span style='font-family:"Calibri",sans-serif'>specific syscall, or file system driver, etc, the bug is almost guaranteed to</span> <br><span style='font-family:"Calibri",sans-serif'>be in that code.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>If you get a rash of crashes with *different* tracebacks, you probably have</span> <br><span style='font-family:"Calibri",sans-serif'>some other code that's overlaying memory.</span> <o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

[-- 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Kernel Panic
  2019-10-22  9:38       ` Christophe DUMONT
@ 2019-10-22 17:20         ` Greg KH
  0 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2019-10-22 17:20 UTC (permalink / raw)
  To: Christophe DUMONT; +Cc: Valdis Klētnieks, kernelnewbies

On Tue, Oct 22, 2019 at 09:38:59AM +0000, Christophe DUMONT wrote:
> Hello, 
> 
>  
> 
> We downgraded to older kernel. We still facing the same Kernel Panic with different Kernel. 

Please contact your vendor for support, they are the only ones that can
support you as it's a very odd and old kernel you are using, and you are
paying for support for it already.  Might as well take advantage of it!

good luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 11+ messages in thread

* kernel panic
  2015-10-15 11:23 kernel panic jinzhao
@ 2015-10-16 11:36 ` mulyadi.santosa
  0 siblings, 0 replies; 11+ messages in thread
From: mulyadi.santosa @ 2015-10-16 11:36 UTC (permalink / raw)
  To: kernelnewbies

On Thu, Oct 15, 2015 at 6:23 PM, jinzhao at wingtech.com <jinzhao@wingtech.com>
wrote:

> Dear all:
>      I met a problem as below, what the function of walk_page_range??
> Exception Class: Kernel (KE)
> PC is at [<ffffffc00017fc90>] walk_page_range+0x3c/0x314
>
> Current Executing Process:
> [Binder_C, 3611][main, 354]
>
> Backtrace:
> [<ffffffc0009f21dc>] __do_kernel_fault.part.5+0x70/0x84
> [<ffffffc0000942f4>] do_bad_area+0x90/0x94
> [<ffffffc000094340>] do_translation_fault+0x30/0x4c
> [<ffffffc0000813fc>] do_mem_abort+0x38/0x98
> [<ffffffc000083c58>] el1_da+0x1c/0x88
> [<ffffffc0001eb3e0>] show_smap+0x88/0x284
> [<ffffffc0001eb5e8>] show_pid_smap+0xc/0x18
> [<ffffffc0001aefb8>] seq_read+0x1a4/0x40c
> [<ffffffc00018e75c>] vfs_read+0x88/0x170
> [<ffffffc00018ebf0>] SyS_read+0x40/0x8c
> [<ffffffc000084308>] cpu_switch_to+0x48/0x4c
> [<ffffffffffffffff>] 0xffffffffffffffff
>
>
> Thanks!
> ------------------------------
> jinzhao at wingtech.cn
>
>
AFAIK, that's the function to get PTE of the related pages, then get the
virtual address of them.

Maybe the caller hit invalid PTE ?

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151016/0ef8f374/attachment.html 

^ permalink raw reply	[flat|nested] 11+ messages in thread

* kernel panic
@ 2015-10-15 11:23 jinzhao
  2015-10-16 11:36 ` mulyadi.santosa
  0 siblings, 1 reply; 11+ messages in thread
From: jinzhao @ 2015-10-15 11:23 UTC (permalink / raw)
  To: kernelnewbies

Dear all:
     I met a problem as below, what the function of walk_page_range??
Exception Class: Kernel (KE) 
PC is at [<ffffffc00017fc90>] walk_page_range+0x3c/0x314 

Current Executing Process: 
[Binder_C, 3611][main, 354] 

Backtrace: 
[<ffffffc0009f21dc>] __do_kernel_fault.part.5+0x70/0x84 
[<ffffffc0000942f4>] do_bad_area+0x90/0x94 
[<ffffffc000094340>] do_translation_fault+0x30/0x4c 
[<ffffffc0000813fc>] do_mem_abort+0x38/0x98 
[<ffffffc000083c58>] el1_da+0x1c/0x88 
[<ffffffc0001eb3e0>] show_smap+0x88/0x284 
[<ffffffc0001eb5e8>] show_pid_smap+0xc/0x18 
[<ffffffc0001aefb8>] seq_read+0x1a4/0x40c 
[<ffffffc00018e75c>] vfs_read+0x88/0x170 
[<ffffffc00018ebf0>] SyS_read+0x40/0x8c 
[<ffffffc000084308>] cpu_switch_to+0x48/0x4c 
[<ffffffffffffffff>] 0xffffffffffffffff


Thanks!


jinzhao at wingtech.cn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151015/440e76ee/attachment.html 

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, back to index

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
2015-10-16 11:36 ` mulyadi.santosa

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git