Bug 4553 - consistant crash with Diamond Stealth 3D 3000
consistant crash with Diamond Stealth 3D 3000
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
5.2
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Preston Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-16 16:01 EDT by jmelson
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-31 16:09:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jmelson 1999-08-16 16:01:06 EDT
I have a consistant system crash or hang when doing startx
for the SECOND time.  First time, log in to console, startx,
everything runs fine, do ctrl/alt/backspace to shut down,
logout, log in (perhaps as another user), startx, and
you get a black screen, and a hung system.  Attempts to
access from net get no response.  Reset button is only
way out.  I'm using XFree86, v 3.3.2.3-25, and the XF86_SVGA
server.  The board has a label on the ROM Stealth 3D 3000
V1.02.
Thanks!
Comment 1 Preston Brown 1999-08-23 10:51:59 EDT
Dave, has this perhaps been fixed with 3.3.3.1 and later?

------- Additional Comments From   08/24/99 00:35 -------
Some additional comments - it looks like hitting the <-- key on the
alpha keyboard area, while communicating with a program using the
character interface in a text window, and then entering the line
that way (showing as Ctrl/h in the window) is related to the crash,
even if this character was entered days before shutting down and
restarting XFree86.
Comment 2 Preston Brown 1999-08-31 16:09:59 EDT
The virge driver has seen a lot of work since 3.3.2.3.  Please try the
3.3.3.1 release which is currently available for 5.2, and if that
doesn't work, upgrade to the forthcoming 3.3.5 release.  If neither of
these fixes your problem, please re-open the bug.

Note You need to log in before you can comment on or make changes to this bug.