From: george anzinger <george@mvista.com>
To: Effrem Norwood <enorwood@effrem.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange frequent message
Date: Mon, 07 Oct 2002 10:08:45 -0700 [thread overview]
Message-ID: <3DA1BF9D.30A214E1@mvista.com> (raw)
In-Reply-To: CFEAJJEGMGECBCJFLGDBAEAFCFAA.enorwood@effrem.com
Effrem Norwood wrote:
>
> Hi all,
>
> I'm using a 2.4.18 kernel with QLogic 6.1 Beta 5 qlaxxxx drivers patched in
> and compiled as part of the kernel rather than as a module. Dual Xeon 2.4,
> 2.0GB ram, highmem enabled (4GB), SuperMicro MB. ACPI is disabled on the MB
> as well as in the kernel.
>
> I keep getting these weird messages:
>
> "Uhhuh. NMI received for unknown reason 2c. Dazed and confused, but trying
> to continue Do you have a strange power saving mode enabled?"
>
> "Uhhuh. NMI received for unknown reason 3c. Dazed and confused, but trying
> to continue Do you have a strange power saving mode enabled?"
>
> Any ideas why this is happening?
It comes from traps.c do_nmi() when it can not decode the
NMI reason. If all else fails you may want to alter the
code to turn it into an Oops and see what turns up. Check
the "die" code for how to break the locks you need to
actually do an Oops from an NMI.
-g
>
> Please cc me on replies to this as the list volume is too great for me to
> subscribe.
>
> My thanks,
>
> Eff Norwood
>
> -
> 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/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
prev parent reply other threads:[~2002-10-07 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 15:41 strange frequent message Effrem Norwood
2002-10-07 17:08 ` george anzinger [this message]
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=3DA1BF9D.30A214E1@mvista.com \
--to=george@mvista.com \
--cc=enorwood@effrem.com \
--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