From: Ian Molton <spyro@armlinux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon PSE/AGP Bug
Date: Tue, 22 Jan 2002 23:21:12 +0000 [thread overview]
Message-ID: <20020122232112.3ccdb3d5.spyro@armlinux.org> (raw)
In-Reply-To: <1011711077.10474.3.camel@psuedomode>
In-Reply-To: <B575BF98FA79D4119BD20008C7A4516502E1C488@ffz00za9.wwz1me.mail.dresdner.net> <1011711077.10474.3.camel@psuedomode>
On a sunny 22 Jan 2002 09:51:12 -0500 Ed Sweetman gathered a sheaf of
electrons and etched in their motions the following immortal words:
> I've had two different kinds of athlon's (K7-2 and Tbird 1.33Ghz) with
> V3 agp and Matrox G450 agp but both of the times it was on Abit
> motherboards
> I dont deny the existance of the "bug" in linux but it's just strange
> how a cpu bug is turning up with some people and not others. Perhaps
> only some chips from all the batches are affected? whatever the case
> tuxracer works perfectly here.
Same here. I have a Duron 800 (running at 1GHz) on an ASUS A7M with a
Radeon 64 DDR VIVO, and its running SWEEEET at AGP 4x.
next prev parent reply other threads:[~2002-01-22 23:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 14:12 Athlon PSE/AGP Bug Halpaap, Mark (CETA)
2002-01-22 14:51 ` Ed Sweetman
2002-01-22 23:21 ` Ian Molton [this message]
2002-01-22 14:51 ` João Seabra
2002-01-23 18:49 ` Marek Mentel
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 17:59 Ben Carrell
2002-01-21 10:53 Reid Hekman
2002-01-21 13:37 ` David S. Miller
2002-01-21 13:50 ` Arjan van de Ven
2002-01-21 16:58 ` jepler
2002-01-21 17:26 ` Ed Sweetman
2002-01-21 22:14 ` David S. Miller
2002-01-21 16:54 ` Andrea Arcangeli
2002-01-21 17:57 ` Reid Hekman
2002-01-21 18:17 ` Andrew Morton
2002-01-21 19:11 ` Harold Campbell
2002-01-21 22:23 ` David S. Miller
2002-01-22 0:39 ` Andrea Arcangeli
2002-01-22 1:08 ` David S. Miller
2002-01-22 7:05 ` Ville Herva
2002-01-22 7:08 ` David S. Miller
2002-01-22 8:05 ` Daniel Robbins
2002-01-22 0:26 ` Stuart Young
2002-01-22 0:36 ` Steve Brueggeman
2002-01-22 1:02 ` Steve Brueggeman
2002-01-22 20:13 ` Florian Weimer
2002-01-22 22:14 ` Ed Sweetman
2002-01-22 22:52 ` Steve Brueggeman
2002-01-22 23:49 ` Rik van Riel
2002-01-23 0:36 ` Stuart Young
2002-01-23 1:20 ` Rene Rebe
2002-01-23 2:01 ` Gustavo Zacarias
2002-01-23 2:11 ` Tom Hornyak
2002-01-22 22:32 ` Steve Brueggeman
2002-01-22 5:45 ` Shaya Potter
2002-01-22 12:58 ` Dave Jones
2002-01-22 15:27 ` Shaya Potter
2002-01-22 18:52 ` Greg
2002-01-22 22:08 ` Rene Rebe
2002-01-21 22:19 ` David S. Miller
2002-01-22 0:37 ` Andrea Arcangeli
2002-01-22 0:43 ` Russell King
2002-01-22 0:53 ` Andrea Arcangeli
2002-01-22 0:55 ` Russell King
2002-01-22 1:07 ` David S. Miller
2002-01-22 1:27 ` Andrea Arcangeli
2002-01-22 16:57 ` David Woodhouse
2002-01-21 19:37 ` Alan Cox
2002-01-21 19:34 ` David Weinehall
2002-01-21 19:53 ` Sipos Ferenc
2002-01-22 6:32 ` Paul G. Allen
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=20020122232112.3ccdb3d5.spyro@armlinux.org \
--to=spyro@armlinux.org \
--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