From: "Paweł Sikora" <pluto@agmk.net>
To: linux-kernel@vger.kernel.org
Cc: arekm@pld-linux.org
Subject: [2.6.38.6] opteron server dies / how to debug call trace flood?
Date: Mon, 23 May 2011 21:45:23 +0200 [thread overview]
Message-ID: <201105232145.23365.pluto@agmk.net> (raw)
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ł.
reply other threads:[~2011-05-23 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201105232145.23365.pluto@agmk.net \
--to=pluto@agmk.net \
--cc=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.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 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.