Red Hat Bugzilla – Bug 58188
system hard locks on specific video setting
Last modified: 2007-04-18 12:38:57 EDT
Description of Problem:
The system will hard lock with little or no activity on a specific
video setting, running a video intensive app will cause the freeze to occur within
Platforms: PE-6650, PE-4600
Kernel: 2.4.7-10smp (up works ok)
Video chip: on-
ati rage xl 8meg.
Resolution: 1600x1200 (only)
Color depth: 16 bit (only)
M780 or P780
Desktop: KDE or Gnome
Desktop Manager: kdm, gdm or xdm
Steps to Reproduce:
1. Install RH 7.2
1600x1200 resolution and 16bit color mode
3. start X, run gears or gloss or some other
intensive app, hard lock should occur within 5 seconds, or may occur before desktop is
A system freeze within seconds of desktop loading, a
not occur on PE-
Also tested at 1600x1200 in 8bit and 24bit ok.
16bit with resolution
Please attach you X configuration file, and X server logs using the
attachment link below.
Also.. Please upgrade your kernel and other packages to the latest
official erratum releases.
This is most likely a kernel issue.
Created attachment 43215 [details]
Created attachment 43216 [details]
Attached log and config for X.
Have tested this with the 2.4.9-13smp kernel and issue still exists.
Dean, please try with kernel 2.4.9-21smp.
Word from AMI may help, or not.
The following video modes are NOT supported under Windows 2000, and could be
related to Linux as well.
Resolution Refresh Rate (Hz) Color Depth
800x600 180 32
1024x768 120 32
1024x768 140 32
1024x768 150 32
1024x768 160 32
1152x864 47 24 and 32
1152x864 60 24 and 32
1152x864 70 24 and 32
1152x864 75 24 and 32
1152x864 80 24 and 32
1152x864 85 24 and 32
1152x864 100 24 and 32
1152x864 120 24 and 32
1280x1024 43 24 and 32
1280x1024 47 24 and 32
1280x1024 60 24 and 32
1280x1024 70 24 and 32
1280x1024 74 24 and 32
1280x1024 75 24 and 32
1280x1024 85 24 and 32
1280x1024 90 24 and 32
1280x1024 100 24 and 32
1600x1200 52 16, 24, and 32
1600x1200 58 16, 24, and 32
1600x1200 60 16, 24, and 32
1600x1200 66 16, 24, and 32
1600x1200 72 16, 24, and 32
1600x1200 75 16, 24, and 32
1600x1200 76 16, 24, and 32
1600x1200 85 16, 24, and 32
It's OK to share with Red Hat.
Note that this issue arises due to the limitation in memory bandwidth of our
current ATI Rage XL implementation. Dell is using a 32 bit frame buffer memory
interface with the Rage XL chip. The stock driver which we have been using was
written for the 64 bit memory interface.
From what you describe above, this seems more like a hardware flaw to
me than a software flaw, however if that is the case, about all we can
do is detect this video card, and disable all of the above video modes,
so that the server does not crash.
Could you please see if it continues to occur with the 4.1.0-15 XFree86
erratum release? If so, please also test the rawhide version of XFree86
and see if that changes anything?
Also, if the above testing turns out to not solve anything, I will
contact ATI myself directly to discuss the problem, and seek assistance
at finding a solution.
Dean, have you tested this with 2.4.9-21 or the new 2.4.9-31 kernel yet?
Jaguar's trying to get out of system test and wants to know what's up with
Mike, any other news from ATI on this?
SOrry for not responding earlier, I've got an updated driver in now that
might work. It's been in the last couple releases. 4.2.0-6.41 being
Can you test it out and update the report?
Problem seems to be fixed with new driver!!
Hampton beta 2
Fantastic. Again, sorry for the delay notifying you of new packages...
bugzilla is becoming a universe of its own to keep track of. ;o)
Thanks for testing and responding so quickly.
Are the new packages slated for:
1) Errata release for 7.2
2) Pensacola release
3) Hampton release
Hampton,however it is possible any erratum released prior to that could also
contain the fix as well.
Update: This bugfix will soon appear in XFree86 4.1.0 erratum packages
for Red Hat Linux 7.1 and 7.2, and also are slated for inclusion in
Pensacola as well.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.