public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pallai Roland <dap@mail.index.hu>
To: linux-kernel@vger.kernel.org
Subject: Re: NMI watchdog question
Date: Tue, 08 Mar 2005 03:28:52 +0100	[thread overview]
Message-ID: <1110248933.8018.229.camel@localhost.localdomain> (raw)


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


             reply	other threads:[~2005-03-08  2:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08  2:28 Pallai Roland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07 10:16 NMI watchdog question Mikael Pettersson
2005-03-07 13:00 ` Pallai Roland
2005-03-06 18:51 Pallai Roland
     [not found] <3EShS-A1-9@gated-at.bofh.it>
2005-03-06 15:14 ` Robert Hancock
2005-03-06  0:53 Pallai Roland
2002-11-06  5:50 george anzinger
2002-11-06 10:53 ` Mikael Pettersson
2002-11-06 17:59   ` george anzinger
2002-11-06 18:12     ` John Levon
2002-11-06 18:58       ` Maciej W. Rozycki
2002-11-06 18:55     ` Maciej W. Rozycki
2002-11-06 19:49       ` george anzinger
2002-11-06 20:07         ` John Levon
2002-11-07 16:20           ` Bill Davidsen
2002-11-07 16:30             ` Maciej W. Rozycki
2002-11-07 16:44             ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1110248933.8018.229.camel@localhost.localdomain \
    --to=dap@mail.index.hu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox