From: Nagy Tibor <nagyt@otpbank.hu>
To: linux-kernel@vger.kernel.org
Subject: 2.4.20 Ooops on Dell 6600
Date: Thu, 15 May 2003 08:16:55 +0200 [thread overview]
Message-ID: <3EC330D7.8060503@dell633.otpefo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 444 bytes --]
Hi,
we have a Dell PowerEdge 6600 server (4x1400 MHz multithread Xeon, 4GB
RAM, SuSe Linux 8.0, 2.4.20 Linux kernel). We have got the attached
'Ooops'. What does it mean?
Thanks for any replay in advance.
------------------------------------------------------------------------
Tibor Nagy
National Savings and Commercial Bank Ltd (OTP Bank)
E-mail: nagyt@otpbank.hu
------------------------------------------------------------------------
[-- Attachment #1.2: Oops.txt --]
[-- Type: text/plain, Size: 955 bytes --]
Oops 0000
CPU 6
EIP 0010:[<c0246400>] Not tained
EFLAGS: 00010246
eax:030ac90a ebx:f8806000 ecx:000003fe edx:01f0c90a
esi:00000001 edi:1f92fc04 ebp:f8806010 esp:ea8bdcec
ds:0018 es:0018 ss:0018
Process rsh (pid: 27741, stackpage=ea8bd000)
Stack: ea8bc000 ea8bdd64 f704df00 ea8bddf8 00002000 1f92fc04 01f0c90a 030ac90a
f8806000 000003fe fe03f800 1f92fc04 01f0c90a 030ac90a c0246467 ea8bdd64
00000000 ea86dd60 ea8bdd64 c0247028 ea8bdd64 00000000 ea8bdde8 c038a6f8
Call Trace: [<c0246467>] [<c0247028>] [<c0220600>] [<c021fe03>] [<c02456c0>]
[<c0220600>] [<c021523c>] [<c0220600>] [<c0220600>] [<c021558f>] [<c0220600>]
[<c021fa29>] [<c0220600>] [<c0234116>] [<c022ef2e>] [<c022efe9>] [<c020af0e>]
[<c022f2ee>] [<c622511f>] [<c02410a6>] [<c0207905>] [<c020761e>] [<c0135fe7>]
[<c0106f23>]
Code: 8b 6d 8b ea 44 24 2c 03 44 24 24 31 d2 f7 74 24 10 8b 4c 24
<0> Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3018 bytes --]
next reply other threads:[~2003-05-15 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 6:16 Nagy Tibor [this message]
2003-05-15 6:40 ` 2.4.20 Ooops on Dell 6600 DevilKin
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=3EC330D7.8060503@dell633.otpefo.com \
--to=nagyt@otpbank.hu \
--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.