From: Jussi Laako <jussi.laako@pp.inet.fi>
To: Alistair J Strachan <alistair@devzero.co.uk>
Cc: Clock <clock@twibright.com>,
kenton.groombridge@us.army.mil, linux-kernel@vger.kernel.org
Subject: Re: nforce2 lockups
Date: 17 Aug 2003 22:27:52 +0300 [thread overview]
Message-ID: <1061148472.1459.3.camel@vaarlahti.uworld> (raw)
In-Reply-To: <200308151738.08965.alistair@devzero.co.uk>
On Fri, 2003-08-15 at 19:38, Alistair J Strachan wrote:
> > > I found your post looking for a solution to my lockups. I bet if you do
> > > a dmesg, you will find that your nforce2 chipset revision is 162.
> >
> > Yeah! Look:
> >
> > NFORCE2: chipset revision 162
>
> 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).
"22:26:25 up 17 days, 11:39, 5 users, load average: 0.06, 0.02, 0.00"
--
Jussi Laako <jussi.laako@pp.inet.fi>
next prev parent reply other threads:[~2003-08-17 19:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <df962fdf9006.df9006df962f@us.army.mil>
2003-08-15 15:15 ` nforce2 lockups 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 [this message]
2003-08-17 20:02 ` Patrick Dreker
2003-08-18 13:28 ` Pavel Machek
[not found] <fa.ih2vscq.35m1rs@ifi.uio.no>
[not found] ` <fa.gbe06ic.1ki851c@ifi.uio.no>
2003-08-17 13:00 ` walt
[not found] <20030817233306.CC67A2D0074@beton.cybernet.src>
2003-08-17 23:41 ` Karel Kulhavý
2003-08-18 8:04 kenton.groombridge
2003-08-18 9:31 ` Ookhoi
2003-08-18 11:00 ` Karel Kulhavý
2003-08-21 1:39 kenton.groombridge
2003-08-21 11:05 ` Patrick Dreker
2003-08-23 1:41 kenton.groombridge
2003-08-23 12:20 Mikael Pettersson
2003-08-23 12:48 ` Patrick Dreker
2003-08-23 15:50 Mikael Pettersson
2003-08-23 18:52 ` Patrick Dreker
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=1061148472.1459.3.camel@vaarlahti.uworld \
--to=jussi.laako@pp.inet.fi \
--cc=alistair@devzero.co.uk \
--cc=clock@twibright.com \
--cc=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).