From: Philippe Elie <phil.el@wanadoo.fr>
To: Zarakin <zarakin@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nmi_watchdog=2 - Oops with 2.6.8
Date: Wed, 25 Aug 2004 18:01:07 +0200 [thread overview]
Message-ID: <20040825160107.GA562@zaniah> (raw)
In-Reply-To: <021101c48a44$c8f846e0$6401a8c0@novustelecom.net>
On Tue, 24 Aug 2004 at 18:42 +0000, Zarakin wrote:
> Hi,
>
> My Gentoo machine will not boot with nmi_watchdog=2 parameter - I get an
> oops at clear_msr_range.
>
> Handwritten oops Info:
> CPU 0
> EIP: 0060: [<0xc0110d4b>] Not tainted
> EIP is at clear_msr_range+0x18/0x25
> eax: 0 ebx:1f ecx: 3ba edx: 0
> esi: 3a0 edi: 1a ebp:0 esp: d7d83f74
> ds: 7b es: 7b ss: 68
> 0xc0110d4b <clear_msr_range+24>: wrmsr
> model : 3
> model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
try this patch please.
--- linux-2.5/arch/i386/kernel/nmi.c~ 2004-06-15 10:52:00.000000000 +0200
+++ linux-2.5/arch/i386/kernel/nmi.c 2004-08-25 17:33:45.000000000 +0200
@@ -376,7 +376,13 @@
clear_msr_range(0x3F1, 2);
/* MSR 0x3F0 seems to have a default value of 0xFC00, but current
docs doesn't fully define it, so leave it alone for now. */
- clear_msr_range(0x3A0, 31);
+ if (boot_cpu_data.x86_model >= 0x3) {
+ /* MSR_P4_IQ_ESCR0/1 (0x3ba/0x3bb) removed */
+ clear_msr_range(0x3A0, 26);
+ clear_msr_range(0x3BC, 3);
+ } else {
+ clear_msr_range(0x3A0, 31);
+ }
clear_msr_range(0x3C0, 6);
clear_msr_range(0x3C8, 6);
clear_msr_range(0x3E0, 2);
next prev parent reply other threads:[~2004-08-25 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:42 nmi_watchdog=2 - Oops with 2.6.8 Zarakin
2004-08-25 6:12 ` Philippe Elie
2004-08-25 9:26 ` Mikael Pettersson
2004-08-25 17:05 ` Philippe Elie
2004-08-25 16:01 ` Philippe Elie [this message]
2004-08-26 3:22 ` Zarakin
2004-08-26 17:02 ` Philippe Elie
[not found] ` <00f801c48bfa$f5ccefb0$6401a8c0@novustelecom.net>
2004-08-27 16:52 ` nmi_watchdog=2 and oprofile " Philippe Elie
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=20040825160107.GA562@zaniah \
--to=phil.el@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=zarakin@hotpop.com \
/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