From: Bubba <bp@dynastytech.com>
To: linux-kernel@vger.kernel.org
Cc: Josh Brooks <user@mail.econolodgetulsa.com>
Subject: Re: CPU failures ... or something else ?
Date: Wed, 25 Dec 2002 20:02:24 -0600 [thread overview]
Message-ID: <200212252002.24898.bp@dynastytech.com> (raw)
In-Reply-To: <20021225175232.O6873-100000@mail.econolodgetulsa.com>
try turning off the Machine Check Exception in the kernel as it is just buggy
on some machines, not necessarily a bug in the kernel, or without
recompiling, use the kernel param "nomce"
On Wednesday 25 December 2002 19:53, Josh Brooks wrote:
> Hello,
>
> I have a dual p3 866 running 2.4 kernel that is crashing once every few
> days leaving this on the console:
>
>
> Message from syslogd@localhost at Tue Dec 24 11:30:31 2002 ...
> localhost kernel: CPU 1: Machine Check Exception: 0000000000000004
>
> Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ...
> localhost kernel: Bank 4: b200000000040151
>
> Message from syslogd@localhost at Tue Dec 24 11:30:32 2002 ...
> localhost kernel: Kernel panic: CPU context corrupt
>
>
>
> Word on the street is that this indicates hardware failure of some kind
> (cpu, bus, or memory). My main question is, is that very surely the
> culprit, or is it also possible that all of the hardware is perfect and
> that a bug in the kernel code or some outside influence (remote exploit)
> is causing this crash ?
>
> Basically, I am ordering all new hardware to swap out, and I just want to
> know if there is some remote possibility that my hardware is actually just
> fine and this is some kind of software error ?
>
> ALSO, I have not been physically at the console when this has happened,
> and have not tried this yet, but whatever that thing is where you press
> ctrl-alt-printscreen and get to enter those post-crash commands - do you
> think that would work in this situation, or does the above error hard lock
> the system so you can't do those emergency measures ?
>
> thanks!
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-12-26 1:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 1:53 CPU failures ... or something else ? Josh Brooks
2002-12-26 1:41 ` Felipe W Damasio
2002-12-26 2:02 ` Bubba [this message]
2002-12-26 3:04 ` Josh Brooks
2002-12-26 22:37 ` Pavel Machek
2002-12-26 3:09 ` Josh Brooks
2002-12-26 3:36 ` J Sloan
2002-12-26 3:39 ` Josh Brooks
2002-12-26 3:20 ` Josh Brooks
2002-12-26 6:03 ` Joseph D. Wagner
2002-12-27 23:30 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 4:21 Billy Rose
2002-12-26 4:48 ` Josh Brooks
2002-12-26 4:03 Billy Rose
2002-12-26 4:04 ` Josh Brooks
2002-12-26 2:05 ` Felipe W Damasio
2002-12-26 6:13 ` Joseph D. Wagner
2002-12-26 6:35 ` Josh Brooks
2002-12-26 6:49 ` Joseph D. Wagner
2002-12-26 7:08 ` Felipe W Damasio
2002-12-26 3:50 Billy Rose
2002-12-26 3:54 ` Josh Brooks
2002-12-26 3:31 Billy Rose
2002-12-26 3:38 ` Josh Brooks
2002-12-26 3:13 Ro0tSiEgE
2002-12-26 3:22 ` Josh Brooks
2002-12-26 6:08 ` Joseph D. Wagner
2002-12-24 20:37 Josh Brooks
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=200212252002.24898.bp@dynastytech.com \
--to=bp@dynastytech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user@mail.econolodgetulsa.com \
/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.