Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 71604 - Chips C&T Xserver locks machine
Chips C&T Xserver locks machine
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-08-15 12:52 EDT by Rob Feuerbach
Modified: 2007-04-18 12:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-15 12:52:28 EDT
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 Rob Feuerbach 2002-08-15 12:52:23 EDT
Description of Problem:
I have a Toshiba Tecra 730XCDT laptop, using the Chips C&T 65550 for video. Upon starting X with the default XF86Config-4 file, after a few minutes 
X locks up, usually when using the mouse. Setting: 'Option "noaccel"' prevents the lockup, but hurt performance.

I think this problem has been tracked down and fixed, and is due to broken Silken Mouse support. (email record at 

When will the patch be implemented into the XFree86 rpms? Thanks.

Version-Release number of selected component (if applicable): 4.2.0-8

How Reproducible: Every time.

Steps to Reproduce:
1. Start X, using default (autodetected) "chips" driver
2. Move the mouse around and wait a few minutes.

Actual Results:
X and the computer locks up. Cannot switch between virtual consoles, cannot ping it.

Expected Results:
X and the computer should continue functioning.

Additional Information:
Comment 1 Mike A. Harris 2002-08-15 13:16:44 EDT
The chips driver in rawhide has bugfixes from XFree86 CVS included
and will be in the next RHL release.  An erratum release of this
may also occur for 7.3 in the future.

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