From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Cc: cbradney@zip.com.au
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sat, 06 Dec 2003 03:08:00 +0100 [thread overview]
Message-ID: <1070676480.1989.15.camel@big.pomac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Craig Bradney wrote:
> All the interrupts are the same...except:
> 0, timer is now IO-APIC-edge.
Same here...
> Im not getting any NMI counts.. should I use nmi-watchdog=1?
I got nmi counts with nmi_watchdog=2... I never tested with =1... if
you get nmi's 1 lemme know.
> Ian, from looking back, you have an A7N8X-X bios 1007.
> Interesting that my USB hcis are still sharing IRQs there.
Your? i only see one... But you share it with sound and eth0...
> Any idea how I can get them apart, or if I should try.
You could always move eth0 to a different slot. Other than that, you can
do manual config for the irq's in the bios, but it shouldn't be
needed...
> My system was pretty stable as I've stated.. but the patch has changed
> things slightly re the timer.
As i stated in my prev email, i had to do 2 full greps at a sizable
amount of data to recreate the crash... =P
And, please CC since i'm not on this ml =P
--
Ian Kumlien <pomac@vapor.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-12-06 2:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 2:08 Ian Kumlien [this message]
2003-12-06 13:36 ` Catching NForce2 lockup with NMI watchdog - found? Craig Bradney
2003-12-06 13:47 ` Bartlomiej Zolnierkiewicz
2003-12-06 14:42 ` Ian Kumlien
2003-12-06 15:33 ` Craig Bradney
2003-12-06 15:58 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 22:57 merged in bk5 " b
2003-12-10 4:48 ` Bob
2003-12-08 3:21 Ross Dickson
2003-12-08 11:36 ` Craig Bradney
2003-12-08 13:34 ` Ross Dickson
2003-12-08 17:40 ` Bob
2003-12-06 19:33 Ian Kumlien
2003-12-07 0:20 ` Craig Bradney
2003-12-07 0:29 ` Ian Kumlien
2003-12-07 10:32 ` Craig Bradney
2003-12-07 14:54 ` Ian Kumlien
2003-12-06 1:58 Ian Kumlien
2003-12-06 0:55 Ian Kumlien
2003-12-06 1:52 ` Craig Bradney
2003-12-06 4:00 ` Mike Fedyk
2003-12-06 8:23 ` Josh McKinney
2003-12-08 3:12 ` Bob
2003-12-05 20:56 Catching NForce2 lockup with NMI watchdog Allen Martin
2003-12-05 23:49 ` Catching NForce2 lockup with NMI watchdog - found? Prakash K. Cheemplavam
2003-12-05 23:55 ` Prakash K. Cheemplavam
2003-12-06 0:15 ` Craig Bradney
2003-12-06 0:21 ` Prakash K. Cheemplavam
2003-12-06 0:37 ` Craig Bradney
2003-12-08 3:08 ` Bob
2003-12-08 3:06 ` Bartlomiej Zolnierkiewicz
2003-12-08 3:03 ` Bob
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=1070676480.1989.15.camel@big.pomac.com \
--to=pomac@vapor.com \
--cc=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.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