From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: cheuche+lkml@free.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog - found
Date: Sat, 06 Dec 2003 13:24:33 +0100 [thread overview]
Message-ID: <3FD1CA81.9010708@gmx.de> (raw)
In-Reply-To: <20031206081848.GA4023@localnet>
cheuche+lkml@free.fr wrote:
> On Sat, Dec 06, 2003 at 12:49:50AM +0100, Prakash K. Cheemplavam wrote:
>
>>So gals and guys, try disabling cpu disconnect in bios and see whether
>>aopic now runs stable.
>>
>
> Yes that fix it. Well time will tell but I cannot make it crash with
> hdparm -tT or cat /dev/hda so far. I'm dumping hda to /dev/null right
> now.
>
> After testing to make it crash, I used athcool to reenable CPU
> disconnect, and guess what, test after that just crashed the box.
> You found the problem, congratulations.
:-)
Isn't it possible to ad athcool's code into the kernel, maybe into the
pm section or even make it an kernel option. It seems to be a nice
workaround for the time-being.
Prakash
next prev parent reply other threads:[~2003-12-06 12:24 UTC|newest]
Thread overview: 21+ 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 [this message]
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
2003-12-08 10:43 Mikael Pettersson
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=3FD1CA81.9010708@gmx.de \
--to=prakashpublic@gmx.de \
--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).