mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rick Gaudette <Richard.Gaudette@Colorado.EDU>
To: linux-kernel@vger.kernel.org
Subject: X-Windows locks up under concurrent OpenGL (Mesa) and I/O on Athlon
Date: 09 Nov 2001 14:11:18 -0700	[thread overview]
Message-ID: <1005340278.6168.21.camel@wanderer> (raw)

Hi,

I am submitting this to the kernel mailing list on the hunch that
intense system usage appears to be causing a deadlock that goes away
when AGP usage is disabled.

Problem:
X-Windows locks up under concurrent OpenGL (Mesa) and I/O on Athlon
based motherboards with VIA and AMD chipsets and AGP enabled.  This
problem does NOT occur on Pentium III and Pentium IV based systems with
Intel chipsets.  Nor, if AGP is disabled.

Using either OpenGL sample applications (morph3d, teapot), a solar
system simulation app called ssystem, or our own application IMOD along
with concurrent I/O causes all of our Athlon based systems to hang
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
that the app is either using all of CPU cycles or splitting it evenly
with X.

We have tried many hardware combinations that include both VIA and AMD
chipsets, NVIdia and Matrox video cards, below is a list of
motherboards, video cards and RedHat version for which we have observed
and can reproduce this behavior:

CPUs:
  Athlon 1.0 -1.4 GHz
  Athlon MP 1800+

Motherboards:
  IWILL KK-266
  ABIT KT-7/KT-7a/KT-7A-Raid
  ABIT KG-7-RAID
  Tyan Tiger MP (S2460)

Video cards:
  NVidia Geforce2 MX, Ultra
  NVidia Geforce3 and Geforce3 Titanium 500
  Nvidia drivers: 1.0-1512 and 1.0-1541
  Matrox G400 with 1.3 drivers and XFree86 4.0.3 drivers

OS Versions:
  Red Hat 7.1
  Red Hat 7.1 with kernel upgrades from redhat.com
  Red Hat Roswell
  Red Hat Roswell with ALL upgrades from Red Hat Network
  Red Hat 7.2
  SUSE 7.1

Xfree86 versions 4.0.3 and 4.1.0

Typical system config:
  40 GB IDE (ATA-100) hard disk
  Generic CD-ROM
  Generic network card (100BT)
  1-1.5 GB RAM
  400 watt or greater power supply


Reproduction Procedure:
Run an OpenGL app such ssystem
http://linux.tucows.com/home/preview/9981.html or our IMOD
ftp://bio3d.colorado.edu/pub/graphicstest/obj7.mod.gz .  

To run ssystem:
  tar -xzvf solartest.tar.gz
  cd solartest/ssystem
  ./ssystem
  resize thewindow greater than 800x800

To run IMOD:
  gunzip obj7.mod.gz
  imodv obj7.mod
  You should get a 512x512 window with a model displayed in it.
  Type 5 then 6 on the numeric keypad to start the model spinning.


A simple way to do persistent concurrent I/O:
  Create a file called bigfile larger than the RAM size of the computer
  under tcsh 
    while (1)
    \cp bigfile bigfile1
    end


X will appear to hang within 3 hours on all of our machines. Sometimes
the display will hang until the next mouse or keyboard event.  This  is
a bad sign and is usually a precursor to a full hang-up.

Any help with this problem would be greatly appreciated.

To contact us:

Rick Gaudette
rickg@bio3d.colorado.edu



             reply	other threads:[~2001-11-09 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-09 21:11 Rick Gaudette [this message]
2001-11-09 21:29 ` Alan Cox

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=1005340278.6168.21.camel@wanderer \
    --to=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®