Red Hat Bugzilla – Bug 485399
During initial steps of install all IRQ's used are disabled (Disabling IRQ#) and installation hangs.
Last modified: 2009-12-18 02:54:44 EST
Description of problem:
I tried to install F10 on a Compaq Proliant 5000 with 2 Pentium Pro, 1152Mb ram, ATI chipset pci video card(RV100) (IRQ #10), 2 Compaq smart-2 array controllers(Firm.4.50)(IRQ #15 & #5, Embedded scsi controller (Sym 53c825)(IRQ #14), Sil0680 ATA raid controller(IRQ #11) and a Realtek Gigabit lan card(IRQ #9). I gave the normal kernel parameters for Proliant memory (memmap=exactmap memmap=640k@0 memmap=1151m@1m mem=1152m) and the install started:
Loading initrd.img.................(3 rows of dots)....ready
Probing EDD(edd=off to disable).......ok
(then lots of lines I could not catch till:)
anaconda installer init version 188.8.131.52 starting
mounting /proc filesystem... done
creating /dev filesystem... done
mounting /dev/pts (unix98 pty) filesystem... done
trying to remount root filesystem read write... done
mounting /tmp as ramfs... done
Disabling IRQ #8
Disabling IRQ #1
waiting for hardware to initialize...
Disabling IRQ #15
Disabling IRQ #14
after some time (about 2 minutes) I got the language choosing screen but no way to interract with it (tried the numlock key , Ctrl+Alt+Del and nothing happened).
I retried with:
1)irqpoll - no change.
2)noirqdebug - no change except for no messages of disabled IRQ's
3)nolapic - I reached this point:
Running anaconda 184.108.40.206, the Fedora system installer - please wait...
22:25:24 Starting graphical installation...
mini-wm: Fatal IO error 11 (Resource temporarily unavailable) on Xserver :1.0.
anaconda: Fatal IO error 11 (Resource temporarily unavailable) on Xserver :1.0.
install exited abnormally [1/1]
unmounting filesystem... etc.
I then tried:
1)F9 - machine hanged before graphical install.
2)F8 - Installation succesfull (Ferdora (220.127.116.11-42.fc8)) systemwas ok, but after yum update (Fedora (18.104.22.168.57.fc8)) at the reboot:
Red Hat nash version 6.0.19 starting
Disabling IRQ #1
irq 15: nobody cared (try booting with the "irqpoll" option)
[<f885b213>] (do_ida_intr+0x0/0x290 [cpqarray])
Disabling IRQ #15
_ (system hanged)
I tried with the irqpoll option but no changes.
I searched in the release notes and noted the big changes from F8 and F9,F10. Some link with the problem?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
huh? component udev? I think this is kernel!
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.