lkml.org 
[lkml]   [2008]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Bugme-new] [Bug 11543] New: kernel panic: softlockup in tick_periodic() ???
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


\
 
 \ /
  Last update: 2008-09-16 16:19    [W:0.064 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site