Red Hat Bugzilla – Bug 609371
Computer reboots when loging in with Radeon RV410 [X700 (PCIE)]
Last modified: 2011-06-27 15:10:34 EDT
Created attachment 427869 [details]
Description of problem:
With the default settings of Fedora 13 (and all components updated), when I try to login into my account using gdm, my computers reboots instead.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Turn on computer and boot
2. In gdm select the correct user
3. type the password and press enter
2. switch to a virtual console (CTRL-ALT-F2)
3. return to graphic console (ALT-F1)
The computer reboots immediately (some rare times there was a delay but most of the time it is immediate).
Very often during the reboot the bios hangs (the computer beeps). The only fix then is for a full shutdown (hold the power button for 5 s).
If the bios does not block then most of the time linux no longer reaches the login prompt but reboots during the startup. Again the only fix is the full shutdown.
That I can login, or at least that it does not reboot. The X driver might crash but it should not reboot the computer.
The only workaround I have is to disable all acceleration. I have a config file in /etc/X11/xorg.conf.d/ containing:
with that I can login and the gui seems very stable but I have no acceleration, 3D, xv ...
Using nomodeset did not work (the X server will not start at all). But it also did not reboot.
I think this problem has been going on since an update (kernel or xorg-driver) during Fedora 12 (last Fall?)
I installed Fedora 13 by upgrading from Fedora 12.
I will atttacg logs for the default settings (accel which reboots), with noaccel (which works), and nomodeset (which does not work).
For noaccel, the login is completed (password+enter) at Jun 28 11:23:32.
Note that with accel, because of the reboot, the log only goes until the gdm login screen. It contains nothing from the reboot sequence.
Created attachment 427871 [details]
Xorg log with nomodeset kernel option
Created attachment 427874 [details]
Xorg log with default acceleration enabled up to before causing the reboot
Created attachment 427877 [details]
/var/log/message with default accel enabled.
Created attachment 427879 [details]
dmesg with default accel enabled
Created attachment 427880 [details]
xorg log with accel disabled
Created attachment 427881 [details]
/var/log/messages with accel disabled
Created attachment 427882 [details]
dmesg with accel disabled
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I noticed it was no longer a problem when the kernel went to 2.6.34.
I might have been fixed before but that is when I noticed the problem was gone.
kernel-184.108.40.206-54.fc13.x86_64 (09 Sep 2010)
xorg-x11-drv-ati-6.13.0-1.fc13.x86_64 (28 May 2010)
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.