On 17 Jun 2001 17:37:23 +0300, Cedar Cox wrote:
>
> Mar 15 03:36:06 nanu kernel: Uhhuh. NMI received. Dazed and confused, but
> trying to continue
> Mar 15 03:36:06 nanu kernel: You probably have a hardware problem with
> your RAM chips
>
Have you disab
> >NMI = "NonMaskable Interrupt". I have no idea what can be causing this
> >(maybe somebody else here knows?) but the kernel's hunch might be correct :(
--
> >
> But no way of actually knowing what triggered it?
>
> Then again, cosmic rays c
From the 8086 Book,(Osborne/McGraw Hill), circa 1980 (and still the best
reference on entry level real mode 80x86 architexture).
Begin RTFM:
Page 7-4:
NMI is a non-maskable interrupt request input. NMU is an edge triggered input.
Should NMI go from low to high, the 8086 will complete
Source of NMI greatly depends on your hardware brand, since NMI is wired
differently on many motherboards. In my Intel server box, for example,
NMI can be caused by internal "intstrumentation", or diagnostics (like
when some fan RPM drops below certain level, or temperature raises). I
On Sun, 17 Jun 2001 18:34:58 +0300 (EET DST), Omer Zak <[EMAIL PROTECTED]> wrote:
> ..
The subject should have been: "The Effect of Gamma Rays on Marigolds"
(Marigolds are called in Hebrew &lamed;&vav;&tav;&het; &yod;&nun;&resh;&vav;&pe;&yod;&tsadi; - it's a flower name).
BTW. The play by Pa
However, cosmic rays would probably disturb the state of a RAM bit before
being strong enough to affect the voltage on a specific CPU leg.
Then such a disturbance would cause parity errors to happen.
A piece of history:
In the early 1980's, there was a serious problem of "soft errors" in
dynamic
Nadav Har'El wrote:
>On Sun, Jun 17, 2001, Cedar Cox wrote about "NMI?":
>
>>Mar 15 03:36:06 nanu kernel: Uhhuh. NMI received. Dazed and confused, but
>>trying to continue
>>Mar 15 03:36:06 nanu kernel: You probably have a hardware problem with
>>your
On Sun, Jun 17, 2001 at 05:37:23PM +0300, Cedar Cox wrote:
>
> Mar 15 03:36:06 nanu kernel: Uhhuh. NMI received. Dazed and confused, but
> trying to continue
> Mar 15 03:36:06 nanu kernel: You probably have a hardware problem with
> your RAM chips
>
> As you can see, I
On Sun, Jun 17, 2001, Cedar Cox wrote about "NMI?":
>
> Mar 15 03:36:06 nanu kernel: Uhhuh. NMI received. Dazed and confused, but
> trying to continue
> Mar 15 03:36:06 nanu kernel: You probably have a hardware problem with
> your RAM chips
>
> As you can see,
Mar 15 03:36:06 nanu kernel: Uhhuh. NMI received. Dazed and confused, but
trying to continue
Mar 15 03:36:06 nanu kernel: You probably have a hardware problem with
your RAM chips
As you can see, I got this in my syslog quite a while ago.. The server's
been running great and this is the
Matan Ziv-Av wrote:
> On Sat, 1 Apr 2000, Izar Tarandach wrote:
>
> > From arch/i386/traps.c, I came under the impression that parity and
> > other ram errors would get their own messages. On the other hand,
> > anything caused by "other factors" would come up as unknown. Is
> > that not the actu
On Sat, 1 Apr 2000, Izar Tarandach wrote:
> From arch/i386/traps.c, I came under the impression that parity and
> other ram errors would get their own messages. On the other hand,
> anything caused by "other factors" would come up as unknown. Is
> that not the actual case ? What other reasons co
Matan Ziv-Av wrote:
> Some bioses send some apm interrupts even when it is disabled, so you
> might want to compile basic apm support in the kernel. And make sure the
> ram is ok. Do you use true parity or ecc ram?
>From arch/i386/traps.c, I came under the impression that parity and
other ram er
Tzafrir Cohen wrote:
> Did that already today. I still get those messages. Actually - now the
> reason seemsto have changed to "3d" and "2d".
>
> What is the "reason" for an NMI interrupt? Can I learn from that which
> device sent me this interrupt?
e between 2c and 2d (bit 0) is clock 2 enable (the clock used
to drive the speaker). Maybe there was a "beep" at the nmi occured?
Some bioses send some apm interrupts even when it is disabled, so you
might want to compile basic apm support in the kernel. And make sure the
ram is ok. Do you
On Sat, Apr 01, 2000 at 09:33:34PM +0200, Tzafrir Cohen wrote:
> Did that already today. I still get those messages. Actually - now the
> reason seemsto have changed to "3d" and "2d".
>
> What is the "reason" for an NMI interrupt? Can I learn from
Did that already today. I still get those messages. Actually - now the
reason seemsto have changed to "3d" and "2d".
What is the "reason" for an NMI interrupt? Can I learn from that which
device sent me this interrupt?
On Sat, 1 Apr 2000, Udi Finkelstein wrote:
:58 yarden kernel: Uhhuh. NMI received for unknown reason 2c.
>Mar 26 05:18:58 yarden kernel: Dazed and confused, but trying to continue
>Mar 26 05:18:58 yarden kernel: Do you have a strange power saving mode
>enabled?
Well, why don't you listen to the warnings??
Start by turning off A
Hi list
I have a computer with Mandrake 6.1 (kernel 2.2.13).
I recently upgraded most of the hardware. Since then I started getting
messages (every couple of hours):
Mar 26 05:18:58 yarden kernel: Uhhuh. NMI received for unknown reason 2c.
Mar 26 05:18:58 yarden kernel: Dazed and confused, but
19 matches
Mail list logo
