From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: j_kernel@hoblitt.com, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 11543] New: kernel panic: softlockup in tick_periodic() ???
Date: Wed, 17 Sep 2008 17:29:04 +0400 [thread overview]
Message-ID: <20080917132904.GB7309@lenovo> (raw)
In-Reply-To: <20080917131306.GB20626@elte.hu>
[Ingo Molnar - Wed, Sep 17, 2008 at 03:13:06PM +0200]
|
| > Evetually nmi_watchdog=2 does work right? Though it's not good that
| > we've got 8259 spurious interrupt. Hmm...
|
| well, nmi_watchdog=2 changes the layout of clockevent devices and easily
| switches the system into non-highres non-dynticks mode. So it can hide
| bugs.
|
| Ingo
|
and it does since we have nmi stuck on lapics. Still investigating.
- Cyrill -
next prev parent reply other threads:[~2008-09-17 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 2:43 [Bugme-new] [Bug 11543] New: kernel panic: softlockup in tick_periodic() ??? 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 [this message]
2008-09-17 16:27 ` Cyrill Gorcunov
2008-09-17 20:48 ` j_kernel
2008-09-18 7:09 ` Cyrill Gorcunov
[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
2008-09-16 17:56 ` Cyrill Gorcunov
2008-09-16 17:57 ` 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=20080917132904.GB7309@lenovo \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=j_kernel@hoblitt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.