[Top] [All Lists]

Re: System locking: kernel-2.4.6pre3-xfs

To: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Subject: Re: System locking: kernel-2.4.6pre3-xfs
From: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>
Date: Fri, 13 Jul 2001 10:19:27 +0200
>received: from mobile.sauter-bc.com (unknown []) by basel1.sauter-bc.com (Postfix) with ESMTP id 43F3957306; Fri, 13 Jul 2001 10:28:44 +0200 (CEST)
Cc: ptb@xxxxxxxxxx, linux-xfs@xxxxxxxxxxx
Organization: Sauter AG, Basel
References: <2866.995008978@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Keith Owens schrieb:
> On Fri, 13 Jul 2001 08:31:59 +0200,
> Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> wrote:
> >"Peter T. Breuer" schrieb:
> >> succession. On one occasion I saw the crash, and it was the NMI
> >> watchdog kicking in! It said that CPU 1 was locked. The trace was
> >
> >Maybe you have to change some settings in the BIOS Setup. Some
> >'operating systems' need a watchdog to free them from showing
> >a blue screen after some minutes or hours of operation :), but
> >Linux does not need it usually and it's good to disable all
> >those features in the setup (if they exist).
> The NMI watchdog has nothing to do with the BIOS.  It is a feature of
> Linux where we generate non maskable interrupts to catch disabled
> spinloops inside the kernel.  With kdb compiled in and active, the NMI
> watchdog is a very useful debugging aid.

Sorry, I thought it is the watchdog of a 'server managment card'
generating NMI's. Stupid question: what happens if for example Memory
Error Correction generates an NMI because it detected an error?

<Prev in Thread] Current Thread [Next in Thread>