Description of problem: After updating from 2.6.25.4-30.fc9.x86_64 to 2.6.25.6-55.fc9.x86_64 booting hangs between the execution of auditd and restorecond. It seems to always get a status of "Ok" for auditd and sometimes gets a status of "Ok" for restorecond, but never gets pass that stage. Version-Release number of selected component (if applicable): 2.6.25.6-55.fc9.x86_64 How reproducible: Allow the Kernel Update (Including Headers and Devel Packages) to run on Fedora 9 using kernel 2.6.25.4-30.fc9.x86_64 to update the kernel to 2.6.25.6-55.fc9.x86_64. Steps to Reproduce: 1. Allow update for Kernel 2.6.25.4-30.fc9.x86_64 to 2.6.25.6-55.fc9.x86_64 2. Reboot System using (as root) /sbin/shutdown -r now 3. Watch start-up until it hangs as specified. Actual results: Hangs between the execution of auditd and restorecond. It seems to always get a status of "Ok" for auditd and sometimes gets a status of "Ok" for restorecond, but never gets pass that stage. Expected results: Successfully load all start-up programs and bring up the Fedora Stand Login Screen. Additional info:
I would suggest taking audit out of the boot sequence for testing with chkconfig auditd off, then try booting. If you still have a problem, then its not the audit daemon.
Any chance you could isolate the problem by removing the audit daemon from the boot sequence? Thanks.
Sorry for the delay. I have and it still happens. I did was research online and looked into several Fedora forums and many are reporting the issue is with the Wifi drivers. When this release of the kernel loads and initializes the wlan0 device, that is when the kernel panic happens. If the wlan device is disabled, then the panic doesn't happen.
Ok, I see. Then it sounds a lot like this bug should be re-assigned to the kernel since audit is innocent (this time).
I have changed the status of this bug to the Kernel group as suggested by the audit group QA.
(In reply to comment #4) > Ok, I see. Then it sounds a lot like this bug should be re-assigned to the > kernel since audit is innocent (this time). Done... :-)
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.