From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1755494AbYIPOQa@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755494AbYIPOQa (ORCPT <rfc822;w@1wt.eu>);
	Tue, 16 Sep 2008 10:16:30 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753761AbYIPOQV
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 16 Sep 2008 10:16:21 -0400
Received: from www.tglx.de ([62.245.132.106]:36156 "EHLO www.tglx.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753684AbYIPOQU (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 16 Sep 2008 10:16:20 -0400
Date: Tue, 16 Sep 2008 07:14:40 -0700 (PDT)
From: Thomas Gleixner <tglx@linutronix.de>
To: Joshua Hoblitt <josh@hoblitt.com>
cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@linux-foundation.org>,
       linux-kernel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
       j_kernel@hoblitt.com
Subject: Re: [Bugme-new] [Bug 11543] New: kernel panic: softlockup in
 tick_periodic() ???
In-Reply-To: <20080916025431.GB16764@hoblitt.com>
Message-ID: <alpine.LFD.1.10.0809160711360.3606@apollo.tec.linutronix.de>
References: <bug-11543-10286@http.bugzilla.kernel.org/> <20080911170258.aa0bea0d.akpm@linux-foundation.org> <20080912091308.GA10305@elte.hu> <20080913001306.GA9610@hoblitt.com> <20080915210635.GA16764@hoblitt.com> <20080916025431.GB16764@hoblitt.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 15 Sep 2008, Joshua Hoblitt wrote:

> In addition to the deadlocks, we still have the watchdog warning:
> 
> [    0.460034] Testing NMI watchdog ... 
> [    0.532557] WARNING: CPU#0: NMI appears to be stuck (0->0)!
> [    0.533301] Please report this to bugzilla.kernel.org,
> [    0.536635] and attach the output of the 'dmesg' command.
> 
> Perhaps an HPET problem:
> 
> [    0.993800] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
> [    0.999969] hpet0: 3 32-bit timers, 25000000 Hz
> [    1.004396] ACPI: RTC can wake from S4
> [    1.006637] Clockevents: could not switch to one-shot
> mode:<6>Clockevents: could not switch to one-shot mode: lapic is not functional.
> [    1.009844] Could not switch to high resolution mode on CPU 3
> [    1.009848] Clockevents: could not switch to one-shot mode: lapic is not functional.
> [    1.009852] Could not switch to high resolution mode on CPU 2
> [    1.009855] Clockevents: could not switch to one-shot mode: lapic is not functional.
> [    1.009858] Could not switch to high resolution mode on CPU 1
> [    1.009969]  lapic is not functional.
> [    1.056944] Could not switch to high resolution mode on CPU 0

No, that's documented behaviour:

> > > [    0.126660] APIC timer registered as dummy, due to nmi_watchdog=1!

Can you try nmi_watchdog=2 ?

Thanks,

	tglx