From: Gianni Tedesco <gianni@ecsc.co.uk>
To: linux-kernel@vger.kernel.org
Subject: NMI: IOCK error (debug interrupt?) - nope
Date: 19 Dec 2002 10:23:40 +0000 [thread overview]
Message-ID: <1040293420.12106.13.camel@lemsip> (raw)
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Hello,
A firewall of ours recently went tits up (2.4.19). It was still routing
traffic but when I connected to SSH for example the SSH banner would not
appear, it looked like all userspace was dead.
When we looked in the logs there was this. Presumably the hardware is
broken. But I wonder if anyone can confirm this? Thanks!
NMI: IOCK error (debug interrupt?)
CPU: 0
EIP: 0010:[default_idle+34/48] Not tainted
EIP: 0010:[<c0106e12>] Not tainted
EFLAGS: 00000246
eax: 00000000 ebx: c0106df0 ecx: 00000032 edx: 00000019
esi: c02f6000 edi: c02f6000 ebp: c0106df0 esp: c02f7fcc
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c02f7000)
Stack: c0106e92 00000002 00098700 c0105000 0008e000 c02f8759 c028e6c0
0001ffc0
0001ffc0 0001ffc0 0001ffc0 c03404c0 c0100191
Call Trace: [cpu_idle+82/112] [_stext+0/48]
Call Trace: [<c0106e92>] [<c0105000>]
Code: f4 c3 fb c3 8d 76 00 8d bc 27 00 00 00 00 fb b8 ff ff ff ff
--
// Gianni Tedesco (gianni at ecsc dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-12-19 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 10:23 Gianni Tedesco [this message]
2002-12-23 15:12 ` [PATCH]: Re: NMI: IOCK error (debug interrupt?) - nope Gianni Tedesco
2002-12-23 15:28 ` Dave Jones
2002-12-23 16:41 ` Randy.Dunlap
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=1040293420.12106.13.camel@lemsip \
--to=gianni@ecsc.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox