Description of problem: After having a panic, or by forcing one, the kdump kernel boots and is stuck after attempting to detect/classify memory. After rebooting and building a new kdumprd, then rebooting again 1: The kdump kernel doesn't start up if fibre is disconnected. 2: Nor does it work if the fibre cards are unplugged. 3: Nor does it work if the ethernet cards are unplugged. System seems to hang at the same point in the boot, screenshot to be attached. Version-Release number of selected component (if applicable): initrd-2.6.18-120 with hotfix from bz470074 How reproducible: Every time Additional info: Regular kernel seems to boot fine. Screenshot to be attached. I dont have the kdump skills to debug this properly.
Created attachment 331387 [details] Screenshot of stuck location.
what is initrd-2.6.18-120? What version of kexec and kernel are you running? whats your kdump.conf look like? what kind of system is this? Can you attach a sysreport?
Created attachment 332890 [details] Kdump.conf from system. Kdump.conf from system.
Created attachment 332891 [details] sysconfig/kdump from system.
Update: The system seems to hang there, regardless of the state of the ethernet devices or the fiber connections. Kdump configs attached.
This is a dupe of 462519, pretty clearly. *** This bug has been marked as a duplicate of bug 462519 ***