linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cheuche+lkml@free.fr
To: linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog - found
Date: Sat, 6 Dec 2003 09:18:49 +0100	[thread overview]
Message-ID: <20031206081848.GA4023@localnet> (raw)
In-Reply-To: <3FD1199E.2030402@gmx.de>

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.

If you experience crashes with apic and your bios does not have such
option, try athcool at
http://members.jcom.home.ne.jp/jacobi/linux/softwares.html
Its purpose is to *enable* cpu disconnect but can also disable it. Your
best bet is to run it to disable cpu disconnect the soonest possible at
boot.

On the other hand, it isn't the cause of IRQ7 rogue interrupts. As I
initially suspected, it seems now totally unrelated. The ACPI override
handling may be buggy ? Since putting back the timer on IO-APIC-edge
solves it.

Nevertheless this is still a problem, other chipsets for Athlon
processors seems to be able to have cpu disconnect and ioapic enabled
without any crashes. But so far I don't see any thermal differences, I'm
happy with that.

Mathieu

  parent reply	other threads:[~2003-12-06  8:18 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   ` cheuche+lkml [this message]
2003-12-06 11:22     ` Catching NForce2 lockup with NMI watchdog - found 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
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=20031206081848.GA4023@localnet \
    --to=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).