Red Hat Bugzilla – Bug 199577
Regression in drv-ati-220.127.116.11
Last modified: 2018-04-11 08:54:53 EDT
Description of problem:
System crashes, with service light indicating hardware failure.
After upgrading to 18.104.22.168 my system started to crash once or twice a day. No
debugg possible since I even had to unplug it for a reboot.
After my experience with:
I expected it to be the upgraded ati driver. Backed it out and run 22.214.171.124-4
for over a week now without any problems. Well no dri, with got lost when
upgrading from fc4 to fc5.
Version-Release number of selected component (if applicable):
Once or twice a day.
Steps to Reproduce:
1. Use system
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Is your system identical to the one described in bug 152648? Please attach your
X server config file (/etc/X11/xorg.conf) and X server log file
(/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
Otherwise, you may try to upgrade to FC6
(http://fedoraproject.org/wiki/Distribution), which has many issues in FC5 resolved.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Fedora Core 5 is no longer supported, please, could you reproduce this bug with
the updated version of the currently supported distribution (Fedora Core 6, or
Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please
let us know in this bug report. If after a month's time we have not heard back
from you, we will have to close this bug as CANTFIX/INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
No information requested was provided, so I close this bug as INSUFFICIENT_DATA.
Reporter, if you could, please, reopen with additional information.