public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Knight <tegeran@home.com>
To: "Paul G. Allen" <pgallen@randomlogic.com>,
	Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: Sun, 12 Aug 2001 18:50:06 -0700	[thread overview]
Message-ID: <01081218500600.02092@c779218-a> (raw)
In-Reply-To: <20010812155520.A935@ulthar.internal.mclure.org> <200108130100.f7D10YH07664@penguin.transmeta.com> <3B772E5A.392C37E8@randomlogic.com>
In-Reply-To: <3B772E5A.392C37E8@randomlogic.com>

On Sunday 12 August 2001 06:33 pm, Paul G. Allen wrote:
> Linus Torvalds wrote:
<snip>
> > Also, if you followed the other thread on the Tyan Thunder lockup,
> > you'll have noticed that it locked up under heavy PCI loads. At least
> > on that machine it stopped with the 2.4.8 driver.
>
> I hadn't read the entire thread, but I did see that heavy loads seemed
> to be a problem. I am running a GeForce 3 and when I play games or do
> other graphics related things - I have a few OpenGL projects I've been
> working on - I try sqeak every bit of detail and piece of "eye candy" I
> can out of the system, as well as the best available sound. I'd say
> running Quake 3 at 1600x1200x32 in multiplayer should be a heavy load
> on everything, including PCI.

Not neccisarily, the primary load when playing/displaying anything on a 
GeForce card is on the processor and the AGP bus, not the PCI, even the 
NIC wouldn't be putting too much load on PCI. If you had other 
configuration issues that Q3 accessing the HDD a lot, then you might have 
a high load on the PCI bus. (if you do, feel free to contact me 
privately, I may be able to help you tweak things so that you don't get a 
lot of HDD access under Q3)

<snip>

  reply	other threads:[~2001-08-13  1:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-12  2:52 Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Eric S. Raymond
     [not found] ` <997611708.29909.22.camel@DESK-2>
2001-08-12 10:23   ` Jeffrey Ingber
2001-08-12 12:04     ` Alan Cox
2001-08-12 18:31       ` Manuel McLure
2001-08-12 20:15         ` Alan Cox
2001-08-12 20:30           ` Nerijus Baliunas
2001-08-13  3:27             ` Robert Love
2001-08-12 20:35           ` Manuel McLure
2001-08-12 21:59             ` Manuel McLure
2001-08-12 22:24             ` Linus Torvalds
2001-08-12 22:55               ` Manuel McLure
2001-08-12 22:59                 ` Linus Torvalds
2001-08-12 23:15                   ` Manuel McLure
2001-08-13  0:36                     ` Paul G. Allen
2001-08-13  1:39                       ` Justin A
2001-08-13  3:08                       ` Mike Frisch
2001-08-13  1:00                     ` Linus Torvalds
2001-08-13  1:33                       ` Paul G. Allen
2001-08-13  1:50                         ` Nicholas Knight [this message]
2001-08-12 22:10           ` Linus Torvalds
2001-08-12 22:18             ` Alan Cox
2001-08-12 22:21               ` Dax Kelson
2001-08-12 22:31               ` Linus Torvalds
2001-08-16 23:28               ` Pavel Machek
2001-08-17 20:33                 ` Alan Cox
2001-08-13 11:08           ` rui.p.m.sousa
     [not found] <no.id>
2001-08-12 22:30 ` Alan Cox
2001-08-13 12:16 ` Alan Cox
2001-08-13 12:19   ` rui.p.m.sousa
2001-08-13 12:19 ` Alan Cox
2001-08-13 12:35 ` Alan Cox
2001-08-13 12:43   ` Tobias Ringstrom
2001-08-13 12:47 ` Anton Altaparmakov
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 18:53 Ryan C. Bonham
2001-08-13 18:58 ` Daniel T. Chen
2001-08-13 18:54 Anton Altaparmakov
2001-08-13 19:11 Ryan C. Bonham

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=01081218500600.02092@c779218-a \
    --to=tegeran@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgallen@randomlogic.com \
    --cc=torvalds@transmeta.com \
    /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