All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: S2464 (K7 Thunder) hangs -- some lessons learned
Date: Mon, 13 Aug 2001 19:05:32 -0700	[thread overview]
Message-ID: <3B78876C.81460B28@randomlogic.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10108140151000.10879-100000@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:
> 
> > I don't find the errata. Can you hold my hand and point me to it? :)
> 
> hopefully, you looked, and noticed the several "revision guides"
> that AMD makes available.  they contain the errata.  Intel calls
> them "spec updates", I think.

I have the guide and unless it's been updated (the date on the site does not show it has) I have the latest revision of the chipset. (I also noted a DMA and an
AGP issue in a post about two weeks ago).

PGA

-- 
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043

       reply	other threads:[~2001-08-14  1:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10108140151000.10879-100000@coffee.psychology.mcmaster.ca>
2001-08-14  2:05 ` Paul G. Allen [this message]
2001-08-14 11:55 S2464 (K7 Thunder) hangs -- some lessons learned Ryan C. Bonham
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13  1:24 Eric S. Raymond
2001-08-13  1:41 ` Paul G. Allen
2001-08-13  5:12   ` Christopher Abbey
2001-08-13 12:34 ` Alan Cox
2001-08-13 15:18   ` Eric S. Raymond
2001-08-13 15:46     ` Alan Cox
2001-08-13 15:52       ` Eric S. Raymond
2001-08-13 16:00         ` Alan Cox
2001-08-14 21:27           ` Eric S. Raymond
2001-08-14 22:13             ` Alan Cox
2001-08-14  1:45       ` 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=3B78876C.81460B28@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=hahn@physics.mcmaster.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.