linux-kernel - [2.6.38.6] opteron server dies / how to debug call trace flood?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <201105232145.23365.pluto@agmk.net>
Date:	Mon, 23 May 2011 21:45:23 +0200
From:	Paweł Sikora <pluto@...k.net>
To:	linux-kernel@...r.kernel.org
Cc:	arekm@...-linux.org
Subject: [2.6.38.6] opteron server dies / how to debug call trace flood?

Hi,

i'm currently testing the 2.6.38.6 with vserver/grsec on dual opteron
and it dies after some time. afaics on the remote ipmi console there's
a call trace flood without explicite kernel oops. machine respones
to pings but ssh is unavailable. here's the looged ipmi terminal:

(...)
Resource Manager: Runlevel has been reached...........................[ 3 ]

 .------------------------< PLD Linux 2.99 (Th) >------------------------*
:|:
:|:  Welcome to odra
:|:  Mon May 23  2011 19:31:50
:|:
 `---{ 0 users }---[ 2.6.38.6-8 ]---( x86_64 )------*


ttyS1 odra login: [ 3192.210129] Stack:
[ 3192.212164] Call Trace:
[ 3192.213016] Code: 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 8a 10 <eb> f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48 89 e5 
[ 3192.313455] Stack:
[ 3192.315494] Call Trace:
[ 3192.316350] Code: eb ad 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 <f3> 90 8a 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 
[ 3192.416782] Stack:
[ 3192.418813] Call Trace:
[ 3192.419682] Code: 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 <8a> 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48 
[ 3192.520109] Stack:
[ 3192.522135] Call Trace:
[ 3192.523015] Code: 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 <8a> 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48 
[ 3192.626777] Stack:
[ 3192.628810] Call Trace:
[ 3192.629682] Code: 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 <8a> 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48 
[ 3192.833431] Stack:
[ 3192.835461] Call Trace:
[ 3192.836350] Code: 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 <8a> 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48 
[ 3192.936757] Stack:
[ 3192.938792] Call Trace:
[ 3192.939685] Code: 90 90 90 90 90 90 90 55 48 c7 c0 d0 dd 00 00 48 89 e5 65 48 03 04 25 08 b5 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 <8a> 10 eb f6 c9 c3 66 0f 1f 44 00 00 55 48 c7 c0 d0 dd 00 00 48
(...)

is there any way to decrypt such flood?

BR,
Paweł.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/