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() ???
Date: Tue, 16 Sep 2008 07:14:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0809160711360.3606@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080916025431.GB16764@hoblitt.com>
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
next prev parent reply other threads:[~2008-09-16 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11543-10286@http.bugzilla.kernel.org/>
2008-09-12 0:02 ` Andrew Morton
2008-09-12 2:54 ` j_kernel
2008-09-12 2:57 ` Andrew Morton
2008-09-12 9:13 ` Ingo Molnar
2008-09-13 0:13 ` Joshua Hoblitt
2008-09-15 21:06 ` Joshua Hoblitt
2008-09-16 2:54 ` Joshua Hoblitt
2008-09-16 14:14 ` Thomas Gleixner [this message]
2008-09-16 17:56 ` Cyrill Gorcunov
2008-09-16 17:57 ` Cyrill Gorcunov
2008-09-17 2:43 j_kernel
2008-09-17 7:13 ` Cyrill Gorcunov
2008-09-17 9:20 ` j_kernel
2008-09-17 9:38 ` Cyrill Gorcunov
2008-09-17 12:59 ` Cyrill Gorcunov
2008-09-17 13:13 ` Ingo Molnar
2008-09-17 13:29 ` Cyrill Gorcunov
2008-09-17 16:27 ` Cyrill Gorcunov
2008-09-17 20:48 ` j_kernel
2008-09-18 7:09 ` Cyrill Gorcunov
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=alpine.LFD.1.10.0809160711360.3606@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=j_kernel@hoblitt.com \
--cc=josh@hoblitt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome