From: Pascal Schmidt <der.eremit@email.de>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 2.5] report unknown NMI reasons only once
Date: Sun, 20 Apr 2003 01:17:49 +0200 [thread overview]
Message-ID: <E1971af-0002vN-00@neptune.local> (raw)
In-Reply-To: <20030419230019$7cdc@gated-at.bofh.it>
On Sun, 20 Apr 2003 01:00:19 +0200, you wrote in linux.kernel:
>> Those NMIs happen only rarely when the machine is lightly loaded, but
>> under load, I get several of them per second. This quickly makes
>> /var/log/messages grow.
>
> I guess they are overheat traps then
At 41 degrees C reported CPU temperature, I don't think so. Even if this
is off by, say, 10 degrees, it's still not a problem. AMD allows 90 degrees
for my CPU type (Athlon XP 1700+, Thoroughbred core).
Maybe I should add that "under load" in this case means running OpenGL
games using DRI on a Voodoo4 card.
>> I don't think reporting any of those NMIs more than once provides
>> valuable information, so I've cooked up a patch which only reports each
>> unknown NMI reason once.
>
> Its sitting there saying "Something is wrong" "Something is still
> wrong".
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.
--
Ciao,
Pascal
next parent reply other threads:[~2003-04-19 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030419183013$0e6c@gated-at.bofh.it>
[not found] ` <20030419230019$7cdc@gated-at.bofh.it>
2003-04-19 23:17 ` Pascal Schmidt [this message]
2003-04-20 5:03 ` [PATCH 2.5] report unknown NMI reasons only once Zwane Mwaikambo
[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
2003-04-20 14:32 ` John Bradford
2003-04-20 14:58 ` Pascal Schmidt
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=E1971af-0002vN-00@neptune.local \
--to=der.eremit@email.de \
--cc=alan@lxorguk.ukuu.org.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