From: kenton.groombridge@us.army.mil
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Thu, 21 Aug 2003 10:39:19 +0900 [thread overview]
Message-ID: <2224f3e221f996.221f9962224f3e@us.army.mil> (raw)
I downloaded and applied the acpi patch patch_2.4.22-rc2_to_acpi-2.4-20030813.bz2 from:
http://sourceforge.net/project/showfiles.php?group_id=36832
and it did cure my spurious interrupt problem, but unfortunately, my lockups have returned.
It is strange that kernel 2.4.22-rc2 had never locked up at all (only with apic enabled). Ran it for a good week or so with absolutely no lockup (again, only with apic enabled). I tried my best to make it lockup and it never did, but the spurious interrupts made any device that loaded with IRQ 16 and above pretty much worthless. If I disabled apic, my lockups returned.
So there was something about 2.4.22-rc2 (with acpi enabled), that prevented lockups (but had tons os spurious interrupts). Something in patch_2.4.22-rc2_to_acpi-2.4-20030813.bz2 cured the spurious interrupts, but brought back the lockups.
Ken Groombridge
----- Original Message -----
> > I have ASUS A7N8X Deluxe mobo with nForce2 rev 162 without any
> problems> (if not counting unability to enabe SiI SATA DMA mode
> with attached
> > Seagate Barracuda drive).
>
> I have the exact same Board (except I'm not using SATA), and it's
> a nightmare.
> Best uptime so far: a little more than 16 hours. Usually it locks
> up a lot
> earlier. When I do network transfers I can cause it to lock within
> a few
> minutes. Under "the other OS" it runs without any problems.
>
> - --
> Patrick Dreker
next reply other threads:[~2003-08-21 1:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 1:39 kenton.groombridge [this message]
2003-08-21 11:05 ` nforce2 lockups Patrick Dreker
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` Clock
2003-08-15 16:38 ` Alistair J Strachan
2003-08-15 19:06 ` Clock
2003-08-15 17:47 ` Alistair J Strachan
2003-08-15 21:15 ` Clock
2003-08-17 19:27 ` Jussi Laako
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
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=2224f3e221f996.221f9962224f3e@us.army.mil \
--to=kenton.groombridge@us.army.mil \
--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).