lkml.org 
[lkml]   [2005]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: NMI watchdog question
From
Date

>> On Mon, 2005-03-07 at 11:16 +0100, Mikael Pettersson wrote:
>> Please try nmi_watchdog=2.
>
> tried, doesn't work.. much less NMI interrupts in /proc/interrupts this
> time

although, nmi_watchdog=1 works well when this crazy module loaded

may it be a hardware bug? or maybe a usual thing that the low-level
drivers can put the hardware to such a situation when NMI's are stopped
or the nmi_die message can't get out? (sorry for this newbie question
and thanks for your replies)


== nofuture.c:

#include <linux/init.h>
#include <linux/module.h>
#include <linux/kernel.h>

int deadlock_init(void)
{
local_irq_disable();
while ("I want to loop!")
;

return 0;
}

module_init(deadlock_init);



--
d

-
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/

\
 
 \ /
  Last update: 2005-03-22 14:10    [W:0.040 / U:0.760 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site