From: Gianni Tedesco <gianni@ecsc.co.uk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH]: Re: NMI: IOCK error (debug interrupt?) - nope
Date: 23 Dec 2002 15:12:22 +0000 [thread overview]
Message-ID: <1040656341.23373.18.camel@lemsip> (raw)
In-Reply-To: <1040293420.12106.13.camel@lemsip>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Thu, 2002-12-19 at 10:23, Gianni Tedesco wrote:
> 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?)
Turns out to be a 2bit ECC error. The machine is a dell power-edge 350.
--- linux-2.4.19.orig/arch/i386/kernel/traps.c Mon Dec 23 13:28:32 2002
+++ linux-2.4.19/arch/i386/kernel/traps.c Mon Dec 23 15:11:24 2002
@@ -613,7 +613,7 @@
{
unsigned long i;
- printk("NMI: IOCK error (debug interrupt?)\n");
+ printk("NMI: IOCK error (debug interrupt / ECC RAM error?)\n");
show_registers(regs);
/* Re-enable the IOCK line, wait for a few seconds */
--
// 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 prev parent reply other threads:[~2002-12-23 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 10:23 NMI: IOCK error (debug interrupt?) - nope Gianni Tedesco
2002-12-23 15:12 ` Gianni Tedesco [this message]
2002-12-23 15:28 ` [PATCH]: " 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=1040656341.23373.18.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