Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1463 - XFree86-S3 locks machine
XFree86-S3 locks machine
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-03-09 19:29 EST by jogi
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:
Last Closed: 1999-03-11 18:09:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jogi 1999-03-09 19:29:19 EST
Name        : XFree86-S3                       Distribution:
Version     :                          Vendor: Red
Hat Software
Release     : 1                                Build Date:
Tue Jan 19 00:15:29 1999
Install date: (not installed)                  Build Host:
Group       : X11/XFree86/Servers              Source RPM:
Size        : 2364819                          License: MIT
Packager    : Red Hat Software
Summary     : XFree86 S3 server
Description :

Using this package the machine locks up completly if I
quit the windowmanager. Everytime. This happens on two
machines which are rock solid with XFree- Tested
with several kernel revisions (2.0.36, 2.2.2, 2.2.3).

The used VGA cards are Elsa Winner 1000 Trio and Phoenix
(lspci: S3 Inc. 86C764_1 [Trio 32/64 vers 1)

If you need further informations please let me know.

Oh, the systems are both stock RedHat-5.2 + updates.
Comment 1 jogi 1999-03-10 21:40:59 EST
Sorry, but I was shooting in the wrong direction. I updated XFree86
and KDE at the same time. Using xdm instead of kdm resolved the
problem. Although I am wondering how it is possible that the machine
is really *dead*. No keyboard, no nothing :(


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