From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>,
cheuche+lkml@free.fr, linux-kernel@vger.kernel.org,
Allen Martin <AMartin@nvidia.com>
Subject: Re: [PATCH] Re: Catching NForce2 lockup with NMI watchdog - found
Date: Sat, 06 Dec 2003 16:10:42 +0100 [thread overview]
Message-ID: <3FD1F172.2070601@gmx.de> (raw)
In-Reply-To: <200312061411.37795.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> It is possible :-). Here is a completly untested patch.
>
> [PATCH] fix lockups with APIC support on nForce2
I tried it (applied pacth and *enabled* CPU disconnect in bios) and it
works! Good work. Nevertheless, it is no real fix, just a work-around.
Perhaps somone from nvidia should comment on this...or some APIC guru
needs to take a look into the code.
Prakash
next prev parent reply other threads:[~2003-12-06 15:10 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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
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=3FD1F172.2070601@gmx.de \
--to=prakashpublic@gmx.de \
--cc=AMartin@nvidia.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=cheuche+lkml@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).