Description of problem: kernel hangs while booting, after Creating initial device nodes, this happens on a Dell PowerEdge 2950 It happens for all rawhide kernels I tested. Version-Release number of selected component (if applicable): latest I tested: kernel-2.6.29-0.157.rc6.git2.fc11.x86_64 How reproducible: always Steps to Reproduce: 1. Get a Dell PowerEdge 2950 2. Install F10 3. yum --enablerepo=rawhide update 4. reboot Actual results: system hangs during boot Expected results: rebooting is fine Additional info: last 2 lines printed are: Creating initial device nodes üüüüüüüüüüüüüüü
I see this too, if I try to boot to runlevel 3.
Sometimes this issue happens too in my linux box. < http://www.smolts.org/show?uuid=pub_4fcb818f-090b-4e77-a48b-6e23f8b3fc06 >
I installed from f11 rawhide on my x86_64 system (AMD 9750 x4, 4GB, 2.6.29.2-121.fc11_x86_64), and I experience this problem on every boot. This the last message printed: Creating initial device nodes I followed the kernel debugging steps noted in the wiki but with with no success. The best I could do is get a stack backtrace for each cpu (sysrq l): CPU2: CPU 2: Modules linked in: .... RIP: ... native_safe_halt+0xb/0xd .... Call Trace: ... ? default_idle+0x51/0x7c ....? c1e_idle+0x124/0x12b ....? cpu_idle+0x68/0xb3 ....? start_secondary+0x199/0x19e NOTE: This system was previously running f10 and a 2.6.29-rc kernel.
Created attachment 342202 [details] show_backtrace_all_cpus after boot hang
Created attachment 342203 [details] show_task_states after boot hang
I was able to get the serial console to work so I attached these sysrq dumps. Though, I could never capture the boot log...It always resulted in garbage no matter what baud-rate I tried.
Okay, my problem doesn't look kernel related...There is some problem in mkinitrd. I installed the version from F10 and rebuilt the initrd and it booted fine. Will file there.
Possibly the same as bug 499057 which is marked closed but may not actually be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Whatever it was it seems fixed now.