public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Karsten Wiese <fzu@wemgehoertderstaat.de>
Cc: Fernando Lopez-Lezcano <nando@ccrma.stanford.edu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.19-rc6-rt8
Date: Wed, 29 Nov 2006 07:57:34 +0100	[thread overview]
Message-ID: <20061129065734.GB28258@elte.hu> (raw)
In-Reply-To: <200611282340.21317.fzu@wemgehoertderstaat.de>


* Karsten Wiese <fzu@wemgehoertderstaat.de> wrote:

> Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
> > i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from 
> 
> I saw usb transport errors here before rebooting with
> 	nmi_watchdog=0
> contained in kernel command line.

so nmi_watchdog=1 (or was it nmi_watchdog=2 ?) caused these problems - 
and then nmi_watchdog=0 fixed them? i686? Extremely weird. Does the 
patch below fix the issue perhaps?

	Ingo

Index: linux/arch/i386/kernel/nmi.c
===================================================================
--- linux.orig/arch/i386/kernel/nmi.c
+++ linux/arch/i386/kernel/nmi.c
@@ -932,12 +932,14 @@ notrace __kprobes int nmi_watchdog_tick(
 
 	__profile_tick(CPU_PROFILING, regs);
 
+#if 0
 	/* check for other users first */
 	if (notify_die(DIE_NMI, "nmi", regs, reason, 2, SIGINT)
 			== NOTIFY_STOP) {
 		rc = 1;
 		touched = 1;
 	}
+#endif
 
 	/*
 	 * Take the local apic timer and PIT/HPET into account. We don't
Index: linux/arch/x86_64/kernel/nmi.c
===================================================================
--- linux.orig/arch/x86_64/kernel/nmi.c
+++ linux/arch/x86_64/kernel/nmi.c
@@ -814,12 +814,14 @@ int __kprobes nmi_watchdog_tick(struct p
 
 	__profile_tick(CPU_PROFILING, regs);
 
+#if 0
 	/* check for other users first */
 	if (notify_die(DIE_NMI, "nmi", regs, reason, 2, SIGINT)
 			== NOTIFY_STOP) {
 		rc = 1;
 		touched = 1;
 	}
+#endif
 
 	sum = read_pda(apic_timer_irqs);
 	if (nmi_show_regs[cpu]) {

  parent reply	other threads:[~2006-11-29  7:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27  9:49 2.6.19-rc6-rt8 Ingo Molnar
2006-11-28 13:04 ` rt7 sucess 2.6.19-rc6-rt8 Sergio Monteiro Basto
2006-11-28 22:40 ` 2.6.19-rc6-rt8 Karsten Wiese
2006-11-29  0:04   ` 2.6.19-rc6-rt8 Karsten Wiese
2006-11-29  7:06     ` 2.6.19-rc6-rt8 Ingo Molnar
2006-11-29 13:21       ` 2.6.19-rc6-rt8 Karsten Wiese
2006-11-29  6:57   ` Ingo Molnar [this message]
2006-11-29  9:18 ` 2.6.19-rc6-rt8 Hu Gang
2006-11-29  6:41   ` 2.6.19-rc6-rt8 Ingo Molnar
2006-11-29 14:44     ` 2.6.19-rc6-rt8 Hu Gang
2006-11-29  6:58       ` 2.6.19-rc6-rt8 Ingo Molnar

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=20061129065734.GB28258@elte.hu \
    --to=mingo@elte.hu \
    --cc=fzu@wemgehoertderstaat.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nando@ccrma.stanford.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox