Red Hat Bugzilla – Bug 623890
boot freezes after "Probing EDD(...)...ok"
Last modified: 2011-06-28 10:38:12 EDT
Description of problem:
When booting the system, the line "Probing EDD (edd=off to disable)...ok" is displayed, but then the system is frozen. Only a hard reset will work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot PC
2. at initial splash screen edit kernel parameters to remove rhgb and quiet (if not already removed)
3. hit return to boot.
the following line displayed: "Probing EDD (edd=off to disable) ... ok", then the PC is frozen, and needs hard reset or power cycle.
typical boot messages displayed, along with a successful boot.
I have had this system running in practically the same configuration since RH9. I was running F11 for over two years before I upgraded to F13. I did do a test install on a similar system that did work. The only difference is that the failing system has a SCSI array adapter.
Also, the system will boot after a random number or resets - anywhere from 2 to 50+. Basically hit or miss.
If I do manage to get this system booted I will attach the dmesg boot log.
If you get it to boot, try the 220.127.116.11-37 kernel from updates-testing.
Created attachment 439824 [details]
dmesg output from successful boot
(In reply to comment #1)
> If you get it to boot, try the 18.104.22.168-37 kernel from updates-testing.
That kernel did the same thing.
I have attached a dmesg output from a successful boot (from 22.214.171.124-147 kernel).
Do you get any aditional messages if you remove "rhgb" and "quiet" from the kernel options in /etc/grub.conf ?
I'm not sure if this would be the right place to post this, but I'm hitting this as well with the kernel on the F14 1386 install DVD. I either get a freeze as above or I get a "decompression failed" error whilst the kernel is loading the initrd with the standard "System halted" message straight after. It might also be worth a note that the display is rather garbled when I reach the boot menu.
I'll, er, leave it at that just in case I should be filing this as a new bug. ;)
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:
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.