From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: unlisted-recipients:; (no To-header on input)
Cc: Allen Martin <AMartin@nvidia.com>,
"'Jesse Allen'" <the3dfxdude@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog - found?
Date: Sat, 06 Dec 2003 00:55:23 +0100 [thread overview]
Message-ID: <3FD11AEB.5080305@gmx.de> (raw)
In-Reply-To: <3FD1199E.2030402@gmx.de>
Prakash K. Cheemplavam wrote:
> *maybe* I found the bugger, at least I got APIC more stable (need to
> test whether oit is really stable, compiling kernel right now...):
So, new kernel is up. So far so good:
CPU0
0: 47118 XT-PIC timer
1: 34 IO-APIC-edge i8042
2: 0 XT-PIC cascade
8: 3 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 864 IO-APIC-edge i8042
14: 10 IO-APIC-edge ide0
15: 16 IO-APIC-edge ide1
16: 0 IO-APIC-level Skystar2
18: 7690 IO-APIC-level libata
19: 1910 IO-APIC-level nvidia
20: 43 IO-APIC-level ohci_hcd, eth0
21: 540 IO-APIC-level NVidia nForce2
22: 0 IO-APIC-level ohci_hcd
NMI: 0
LOC: 46934
ERR: 0
MIS: 0
Prakash
next prev parent reply other threads:[~2003-12-05 23:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2003-12-06 8:18 ` Catching NForce2 lockup with NMI watchdog - found cheuche+lkml
2003-12-06 11:22 ` Julien Oster
2003-12-08 3:34 ` Bob
2003-12-08 8:13 ` Bob
2003-12-06 12:24 ` Prakash K. Cheemplavam
2003-12-06 13:11 ` [PATCH] " Bartlomiej Zolnierkiewicz
2003-12-06 15:10 ` Prakash K. Cheemplavam
2003-12-06 15:37 ` Craig Bradney
2003-12-06 15:35 ` Vladimir Grebinskiy
2003-12-08 3:25 ` Bob
2003-12-08 3:18 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2003-12-06 0:55 Catching NForce2 lockup with NMI watchdog - found? 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-06 1:58 Ian Kumlien
2003-12-06 2:08 Ian Kumlien
2003-12-06 13:36 ` 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
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-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-09 22:57 merged in bk5 " b
2003-12-10 4:48 ` 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=3FD11AEB.5080305@gmx.de \
--to=prakashpublic@gmx.de \
--cc=AMartin@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=the3dfxdude@hotmail.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 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.