Date: Fri, 3 Sep 2004 12:32:44 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Florian Schmidt <mista.tapas@gmx.net>
Cc: linux-kernel@vger.kernel.org, rlrevell@joe-job.com,
       felipe_alfaro@linuxmail.org
Subject: Re: lockup with voluntary preempt R0 and VP, KP, etc, disabled
Message-ID: <20040903103244.GB23726@elte.hu>
References: <20040903120957.00665413@mango.fruits.de> <20040903100946.GA22819@elte.hu> <20040903123139.565c806b@mango.fruits.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040903123139.565c806b@mango.fruits.de>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1050
Lines: 24


* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > best would be to enable the NMI watchdog (nmi_watchdog=1 (or 2) boot
> > option) - check that it's working via the attached lockupcli.c
> > userspace code (run it as root). To have an NMI watchdog you need
> > APIC/IOAPIC support in the .config.
> 
> Hmm, my local APIC kinda sux and i had all kinds of trouble using it
> [ERR count went up, stuff didn't work; XT-PIC always worked very well
> here]. So i'm kinda reluctant to compile with APIC. I suppose i can
> compile with it but turn it off via boot option? Or does the watchdog
> need a APIC that actually does stuff? 

in theory you should be able to boot with just the local APIC enabled
and "nmi_watchdog=2" and get a working NMI watchdog. You'll still have
the normal PIC IRQ handling.

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