| To: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: System locking: kernel-2.4.6pre3-xfs |
| From: | Keith Owens <kaos@xxxxxxxxxxxxxxxxx> |
| Date: | Fri, 13 Jul 2001 18:27:28 +1000 |
| Cc: | ptb@xxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | Your message of "Fri, 13 Jul 2001 10:19:27 +0200." <3B4EAF0F.D98631AC@ch.sauter-bc.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Fri, 13 Jul 2001 10:19:27 +0200, Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> wrote: >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? They are distinguished by the presence of error codes in port 0x61. See arch/i386/kernel/traps.c, do_nmi(). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | benchmarks, P.Dixon |
|---|---|
| Next by Date: | Re: benchmarks, Seth Mos |
| Previous by Thread: | Re: System locking: kernel-2.4.6pre3-xfs, Simon Matter |
| Next by Thread: | Re: System locking: kernel-2.4.6pre3-xfs, Luc Lalonde |
| Indexes: | [Date] [Thread] [Top] [All Lists] |