From: walt <wa1ter@myrealbox.com>
To: Patrick Dreker <patrick@dreker.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: Sun, 17 Aug 2003 06:00:14 -0700 [thread overview]
Message-ID: <3F3F7C5E.2070607@myrealbox.com> (raw)
In-Reply-To: <fa.gbe06ic.1ki851c@ifi.uio.no>
Patrick Dreker wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am Sunday 17 August 2003 21:27 schrieb Jussi Laako <jussi.laako@pp.inet.fi>
> zum Thema Re: nforce2 lockups:
>
>>On Fri, 2003-08-15 at 19:38, Alistair J Strachan wrote:
>>
>>>>NFORCE2: chipset revision 162
>>>
>>>I use APIC and ACPI on my EPoX 8RDA+, and I've never had any IO problems.
>>>So it seems unlikely that it is tied to a chipset revision.
>>
>>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.
A friend had lots of problems with his NForce2 mobo until he ran memtest86
and found that the memory was flaky. His machine has been running linux
very well since he replaced the memory. (Heh, two days ago ;-)
I wonder if the NForce2 is a bit fussier about the quality of the memory
than other chipsets.
next parent reply other threads:[~2003-08-17 20:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt [this message]
2003-08-23 15:50 nforce2 lockups Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
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] <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=3F3F7C5E.2070607@myrealbox.com \
--to=wa1ter@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@dreker.de \
/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