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?
>
Do you by any chance have IO-APIC on your mo
> Did that already today. I still get those messages. Actually - now the
> reason seemsto have changed to "3d" and "2d".
The reason is the value of port 0x61. the difference between 2d and 3d
is almost random (bit 4 changes every memory refresh cycle). The
difference between 2c and 2d (bit 0) is
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 that which
> device sent me this interrupt?
Quic
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:
> On Fri, 31 Mar 2000 16:18:42 +0
On Fri, 31 Mar 2000 16:18:42 +0200 (IST), Tzafrir Cohen
<[EMAIL PROTECTED]> wrote:
>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. NM
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 t
