* [2.6.38.6] opteron server dies / how to debug call trace flood?
@ 2011-05-23 19:45 Paweł Sikora
0 siblings, 0 replies; only message in thread
From: Paweł Sikora @ 2011-05-23 19:45 UTC (permalink / raw)
To: linux-kernel; +Cc: arekm
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ł.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-05-23 20:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-23 19:45 [2.6.38.6] opteron server dies / how to debug call trace flood? Paweł Sikora
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.