public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Bj?rn Steinbrink <B.Steinbrink@gmx.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	ak@suse.de
Subject: Re: [PATCH 0/2] i386: Fix two more NMI watchdog bugs
Date: Fri, 8 Jun 2007 22:49:11 +0200	[thread overview]
Message-ID: <20070608224911.3ff6bd18@laptop.hypervisor.org> (raw)
In-Reply-To: <20070608204324.GA25392@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Fri, 8 Jun 2007 22:43:25 +0200 Ingo Molnar (IM) wrote:

IM> 
IM> * Bj?rn Steinbrink <B.Steinbrink@gmx.de> wrote:
IM> 
IM> > Anyway, both are bugs and should be fixed. Maybe we're even lucky and 
IM> > it fixes your hang. *fingers crossed*
IM> 
IM> just to make it clear: the NMI watchdog was working perfectly fine on 
IM> that box (in v2.6.21 and in dozens of kernel releases before that, for 
IM> multiple years) before Andi's cleanup patch. So lets find that bug first 
IM> or revert the cleanups.
IM> 
IM> 	Ingo

None of the patches posted by Björn fix the kernel BUG at
arch/i386/kernel/cpu/perfctr-watchdog.c:126! that occurs when doing
echo 0 > /proc/sys/kernel/nmi_watchdog

Call Trace:
 [<c010c429>] single_msr_unreserve+0xd/0x1a
 [<c010c668>] disable_lapic_nmi_watchdog+0x27/0x35
 [<c0110ac6>] proc_nmi_enabled+0xa0/0xbd
 [<c018550c>] proc_sys_write+0x6f/0x8c
 [<c018549d>] proc_sys_write+0x0/0x8c
 [<c0156e5b>] vfs_write+0x8a/0x10c
 [<c0157317>] sys_write+0x41/0x67
 [<c0103c30>] syscall_call+0x7/0xb

Andi, did you have a patch for that?

Cheers,

	- Udo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-08 20:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 12:52 [1/4] 2.6.22-rc3: known regressions Michal Piotrowski
2007-05-29 14:34 ` Jan Kara
2007-05-29 14:41   ` Florin Iucha
2007-05-30  4:35 ` Sam Ravnborg
2007-06-03 13:02 ` Udo A. Steinberg
2007-06-08  6:02   ` [PATCH] Fix interchanged parameters to release_{evntsel,perfctr}_nmi Björn Steinbrink
2007-06-08  6:41     ` Andrew Morton
2007-06-08 10:58       ` Ingo Molnar
2007-06-08 18:44         ` [PATCH 0/2] i386: Fix two more NMI watchdog bugs Björn Steinbrink
2007-06-08 18:46           ` [PATCH 1/2] i386: Fix NMI watchdog not reserving its MSRs Björn Steinbrink
2007-06-08 18:50           ` [PATCH 2/2] i386: Use the right wrapper to disable the NMI watchdog Björn Steinbrink
2007-06-08 20:43           ` [PATCH 0/2] i386: Fix two more NMI watchdog bugs Ingo Molnar
2007-06-08 20:49             ` Udo A. Steinberg [this message]
2007-06-08 20:57               ` Andrew Morton
2007-06-08 21:13                 ` Udo A. Steinberg
2007-06-08 22:28               ` Andi Kleen
2007-06-09  2:27             ` [PATCH] i386: Fix the K7 NMI watchdog checkbit Björn Steinbrink
2007-06-09  2:33               ` Björn Steinbrink

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=20070608224911.3ff6bd18@laptop.hypervisor.org \
    --to=us15@os.inf.tu-dresden.de \
    --cc=B.Steinbrink@gmx.de \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /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