Red Hat Bugzilla – Bug 849341
kernel 3.5.1 and 3.5.2 fails to boot
Last modified: 2013-07-31 22:16:13 EDT
Created attachment 605331 [details]
Kernel 3.5.2 boot stops at this point. No further messages appear.
Kernels 3.5.1 and 3.5.2 hang before switching to userspace, and running plymouth.
kernel-3.5.1-1.fc17.x86_64 occasionally boots if I remove the rhgb and quiet parameter.
kernel-3.5.2-1.fc17.x86_64 fails to boot even without rhgb and quiet.
Last kernel this hardware can boot is kernel-3.5.0-2.fc17.x86_64
Attaching a screenshot of kernel-3.5.2-1.fc17.x86_64's boot, up until the point it hangs.
Created attachment 605332 [details]
Output of dmidecode
Created attachment 605333 [details]
Output of lspci -vv
Created attachment 605334 [details]
Output of lspci -n
Created attachment 605335 [details]
Output of lsusb -v
This hardware uses nouveau, and does not use the oem blob.
Are you still seeing this with 3.5.5 or 3.6?
Yes, I'm afraid there's still a deadlock somewhere, with the "terminal output gfxterm" option enabled in grub.
After taking out that option, kernels 3.5.2 through 3.5.4 never had a boot failure.
After updating to kernel-3.5.5-2.fc17.x86_64 and putting "terminal output gfxterm" back into grub.cfg, the kernel failed to boot in 3 out of 7 attempts.
The cursor timer fix does seem to help, it got so bad that 3.5.2 pretty much failed to boot all the time.
Haven't yet gathered enough stats for 3.5.5 without "terminal output gfxterm", but so far it seems to be ok.
When 3.5.5 does not deadlock, there's a point where the video card resets, there's brief amount of display garbage and the video noticably changes frequencies.
When 3.5.5, and all earlier kernels, deadlock, the deadlock occurs before that video reset.
Is this still an issue with 3.6.X?
I'm afraid so.
* Uncommented "terminal_output gfxterm" directive in grub.cfg
* Rebooted kernel-3.6.10-2.fc17.x86_64 twice, successfully.
* The next three reboots, the kernel locked up when switching video modes.
* Manually removed 'rhgb quiet' from the kernel command line on two subsequent reboots. Both reboots locked up at the "conflicting hw framebuffer" message that's shown in the screencap, see above.
* Dug out my rescue disk, booted Anaconda, mounted my partition, commented out "terminal_output gfxterm".
* Successfully rebooted.
Never logged this boot failure, in the last four months, with "terminal_output gfxterm" commented out, with all intervening kernels.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17'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 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.