[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080916175629.GE7187@lenovo>
Date: Tue, 16 Sep 2008 21:56:29 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Joshua Hoblitt <josh@...litt.com>, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, bugme-daemon@...zilla.kernel.org,
j_kernel@...litt.com
Subject: Re: [Bugme-new] [Bug 11543] New: kernel panic: softlockup in
tick_periodic() ???
[Thomas Gleixner - Tue, Sep 16, 2008 at 07:14:40AM -0700]
| 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
|
And get apic=debug a try too please. I remember there
was a problem with SB600 on ACPI side (but they should
be already fixed)
- Cyrill -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists