kernels 2.6.33-1.fc13.x86_64 and 2.6.33-8.fc13.x86_64 hang on boot for me; I can hear a click from the speakers and/or see the graphical boot Fedora bubble fill up halfway, then hang w/some display corruption (bubble disappears, or in text mode "Fedora 13" is there 3 times around the screen), nothing except power button helps. Not sure if it's nouveau, but I've tried disabling (blacklisted in /etc/modprobe.d/blacklist.conf, rdblacklist=nouveau at boot) but it doesn't make a difference. Same thing with nomodeset or without it, hangs at the same place in text boot as well. No binary NVIDIA drivers involved, F-12 kernel boots fine (2.6.32.9-67.fc12.x86_64) at the moment. I'm using nv, not nouveau at the moment (nouveau worked last time I tried in F-12, but worse than nv). Not sure how to collect more info, the F-13 kernels don't appear to boot far enough to log anything to /var/log/messages. Smolt profile: http://www.smolts.org/client/show/?uuid=pub_65c08b04-62f5-41b6-94c9-7293d0ff259b
Same thing with all F-13 kernels up to 2.6.33.1-21.fc13.x86_64. What can I do in order to get some output that could shed light on this?
Ditto with 2.6.33.1-22.fc13.x86_64, but the problem does not occur with 2.6.34-0.16.rc2.git0.fc14.x86_64 which I just grabbed from koji (nor the 2.6.32.* F-12 kernels). Whatever I've done with nouveau doesn't seem to have any effect, so I suppose it's something else, adjusting summary accordingly.
Can you test booting in text mode (take 'rhgb quiet' out of the kernel parameters) and see if it changes behaviour, or at least displays some errors? thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Already done that, the way I usually boot for now. No effect except that when the hang occurs, the screen corrupts differently (maybe, hard to tell because it looks already so different) or goes all black. I've also tried booting with noapic, no difference. The hang occurs somewhere while udev is doing its thing, so I've tried setting udev_log="debug" in /etc/udev/udev.conf but failed to get anything resembling useful (and there's a lot of information, and very slow boot). I actually managed to boot once when udev_log was on debug, but not any more on the next few boots with the exact same settings. Maybe the successful one was an accident caused by debug being on and thus the boot being so slow that it somehow circumvented whatever causes it to hang that time?
2.6.33.2-35.fc13.x86_64 from koji boots again, something between it and 2.6.33.1-26.fc13.x86_64 has fixed this for me. (Leaving open for F-13 update to appear, feel free to close if you want.)
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.