User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Build Identifier: After doing the last update the boot process stops at the round blue logo with the f. There are no messages. F19 on the same machine boots normally. I have attempted to extract /var/log/messages from F20 using F19. Reproducible: Always Steps to Reproduce: 1.boot 2.wait 3. attached file of /var/log/messages from F20 last boot attempt
Created attachment 866510 [details] tail of /var/log/messages during failed boot of f20 obtained from f19
When I say last update it is the last one I was able to do since I am unable to boot the system to f20. It is probably not the last one issued. Is there a file I could examine that shows the update record so as to determine which update is the last one I used?
There's not much to go on here. It looks like things get stuck in userspace, possibly waiting for some kevents to happen that never do. Is this a baremetal machine, or a KVM guest? Can you install kernel-debug and see if it boots further, or gives you a crash we can start from?
I was able to install kernel-debug and boot up. It looks like a report was sent somewhere by the bug reporting tool. How does this report get related to the problem? Is there a file on my system that I can send in? The machine is a Microway 4 processor booting off of an SSD. I guess this is bare metal. Both F19 and F20 are available from the same disk.
Using kernel-debug, sometimes the boot hangs at the fedora logo but occasionally it gets far enough to log in. In this case it will look normal for a while but after a few minutes it freezes. After another couple minutes the following messages come out: nouveau E[ DRM] GPU lockup switching to software fbcon nouveau E[Xorg714] failed to idle channel repeated several times nouveau E[Gnome-shell] ... I couldn't get the rest so this looks like a display problem. Maybe the bug should be handed off to whoever is interested in display problems.
I have done a reinstall of f20 from DVD and this problem is then not seen. After yum update the problem re-appears. In the last week I see that the problem now appears in F19 also. So whatever is causing this is a recent change to something. It can probably be found in the last F19 update. The only thing that will now boot and stay up is the F20 rescue kernel which I am using now. The machine is a Microway x86-64 4 processor. The "disk" is a SSD. I wonder if the much faster solid state disk can be causing timing problems.
Some folk on the forum report this problem occurring on "older" systems. I finally replaced the video card with a more modern one. Not that it is a fix but it does cause this problem to go away. Jim
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.