Hide Forgot
Description of problem: System will stop to load on any kernel releases after kernel-3.3.0-0.rc3.git2.2.fc18.x86_64. Version-Release number of selected component (if applicable): Any kernel after 3.3.0-0.rc3.git2.2.fc18.x86_64. How reproducible: Always. Steps to Reproduce: 1. Update system to latest Rawhide kernel; 2. Issue a reboot command; Actual results: System will stop after extraction of the vmlinuz and switching of the screen resolution. Expected results: System should boot up to full Linux environment. Additional info: Base Board Information Manufacturer: ASRock Product Name: A75M-HVS BIOS Information Vendor: American Megatrends Inc. Version: P1.60 Release Date: 10/28/2011 CPU: AMD A6-3500 APU with Radeon(tm) HD Graphics
Can you remove the 'rhgb' and 'quiet' from the kernel command line in the grub entry and tell us if there is anything else printed? Is the machine accessible via the network? Can you ping it or ssh into it? Does the light on the capslock key toggle off/on when you hit it?
Thanks, I tried your instructions on kernel 3.3.0-0.rc4.git1.2.fc18.x86_64 and I see interesting stuff happening: up to 5 seconds it is dealing with drm some pause at 9 seconds a message about udev stack depth a bit bigger pause at 25 seconds dracut kicks in and all the rest of commands issued will start slowly go up. each step is about 20 seconds apart. I regained a system login prompt in about 520 seconds! So, it seems the kernel is still starting up, but all is a very slow process. Note: The system is running off a SSD drive.
Created attachment 565359 [details] system booting up with latest rawhide kernel The dmesg log of the slow booting
Created attachment 565360 [details] much quicker bootup with an older kernel older kernel bootup
There was a bad patch included in 3.3.0-0.rc4.git1.2. Can you try 3.3.0-0.rc4.git3.1 (or any kernel after and including 3.3.0-0.rc4.git1.4)? The slowness might be a duplicate of bug 795050
Thanks. It seems that it is the same case as update to kernel 3.3.0-0.rc4.git3.1.fc18.x86_64 resolved that issue for now.