From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Rick Gaudette <Richard.Gaudette@Colorado.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X-Windows locks up under concurrent OpenGL (Mesa) and I
Date: Fri, 9 Nov 2001 22:42:43 MET-1 [thread overview]
Message-ID: <8B83CB50455@vcnet.vc.cvut.cz> (raw)
On 9 Nov 01 at 14:11, Rick Gaudette wrote:
> within a couple of hours. We can usually ssh into the hung machine from
> another machine and kill the application to bring back X. Top shows
Happy you.
> CPUs:
Dual PIII / 800MHz.
> Motherboards:
Gigabyte GA-6VXD7 (with VIA694X)
> Video cards:
G450 with XF 4.1.0 drivers.
> OS Versions:
Debian.
> Typical system config:
45GB IDE
256MB RAM
> A simple way to do persistent concurrent I/O:
Watching fbtv on second G450 head. It stresses AGP as it generates
30MBps stream from PCI -> AGP...
> Any help with this problem would be greatly appreciated.
... and machine is dead - poweroff button does not work. I always thought
that it is specific to VIA chipsets, as almost same configuration (PII
instead of PIII) worked fine on GA-6BXDS (i440BX), and it is new to me
that AMD has same troubles. Help is simple - do not use VIA chipsets,
at least I did not found any other way how to get it to work
(except disabling mainmemory,PCI->AGP transfers (CPU->AGP are OK,
obviously...)).
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: If you have dualhead G400 on VIA and two bt848 grabbers, just run
one fbtv -k on first head, and another fbtv -k on second head. It will
die as soon as you hit enter on second fbtv (and of course they must be
in <=16bpp, as 694X does not handle even one memory stream needed for
32bpp full PAL PCI->AGP transfer).
next reply other threads:[~2001-11-09 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 22:42 Petr Vandrovec [this message]
2001-11-09 22:12 ` Dan Hollis
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=8B83CB50455@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Richard.Gaudette@Colorado.EDU \
--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
all inboxes | Powered by JetHome®