From: Pascal Schmidt <der.eremit@email.de>
To: linux-kernel@vger.kernel.org
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: [PATCH 2.5] report unknown NMI reasons only once
Date: Sun, 20 Apr 2003 16:09:35 +0200 [thread overview]
Message-ID: <E197FVf-0000GS-00@neptune.local> (raw)
In-Reply-To: <20030420052007$742b@gated-at.bofh.it>
On Sun, 20 Apr 2003 07:20:07 +0200, you wrote:
>> Beats me as to what could be wrong. It's not a memory problem and the
>> CPU does not overheat.
>>
>> I'll go patch the kernel for my personal use then, but I'm not the only
>> one seeing those messages without any system problems.
>
> It's all fun and games until NMIs turn into MCEs...
I have the MCE polling stuff enabled and will keep an eye on it. So far
I suspect flaky motherboard design (Athlon XPs didn't even exist when
this piece of hardware was designed).
It's definitely CPU-related since it never happened with the Duron
processor that I used before.
--
Ciao,
Pascal
next parent reply other threads:[~2003-04-20 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030419232008$7a8a@gated-at.bofh.it>
[not found] ` <20030419232008$6291@gated-at.bofh.it>
[not found] ` <20030419232008$5be3@gated-at.bofh.it>
[not found] ` <20030420052007$742b@gated-at.bofh.it>
2003-04-20 14:09 ` Pascal Schmidt [this message]
2003-04-20 14:32 ` [PATCH 2.5] report unknown NMI reasons only once John Bradford
2003-04-20 14:58 ` Pascal Schmidt
[not found] <20030419183013$0e6c@gated-at.bofh.it>
[not found] ` <20030419230019$7cdc@gated-at.bofh.it>
2003-04-19 23:17 ` Pascal Schmidt
2003-04-20 5:03 ` Zwane Mwaikambo
2003-04-19 18:21 Pascal Schmidt
2003-04-19 21:59 ` Alan Cox
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=E197FVf-0000GS-00@neptune.local \
--to=der.eremit@email.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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