Fedora Account System
Red Hat Associate
Red Hat Customer
I tried new Fedora 12 x86_86-Live-KDE and -DVD but both give following error: Kernel:do_IRQ: 0.84 No irq handler for vector... Turning off the live version there was allso a line: Rpc idamapd Kernel:do_IRQ: 0.84 No irq handler for vector... (if I remeber right) Steps to Reproduce: Just try to boot from DVD or Live-USB. Additional info: ASRock 4coredual-vsta/a/asr -mother board with Intel Core 2 E8420 -processor.
this problem is not existing if you use this kernel 2.6.31.5-127.fc12.x86_64 but if you use the new kernel 2.6.32.9-70.fc12.x86_64 i get this message from syslogd in different time kernel: do_IRQ: 5.118 No irq handler for vector (irq -1) kernel: do_IRQ: 2.147 No irq handler for vector (irq -1) kernel: do_IRQ: 5.151 No irq handler for vector (irq -1) kernel: do_IRQ: 5.158 No irq handler for vector (irq -1) kernel: do_IRQ: 2.146 No irq handler for vector (irq -1) kernel: do_IRQ: 2.88 No irq handler for vector (irq -1) kernel: do_IRQ: 2.232 No irq handler for vector (irq -1) kernel: do_IRQ: 5.106 No irq handler for vector (irq -1) kernel: do_IRQ: 5.228 No irq handler for vector (irq -1) kernel: do_IRQ: 5.183 No irq handler for vector (irq -1) kernel: do_IRQ: 2.71 No irq handler for vector (irq -1) kernel: do_IRQ: 1.153 No irq handler for vector (irq -1) kernel: do_IRQ: 2.116 No irq handler for vector (irq -1) the irqbalance process is running on the both Kernel. this a part from #dmesg DMAR:[DMA Read] Request device [06:00.0] fault addr 0 DMAR:[fault reason 06] PTE Read access is not set DRHD: handling fault status reg 702 DMAR:[DMA Read] Request device [06:00.0] fault addr 0 DMAR:[fault reason 06] PTE Read access is not set DRHD: handling fault status reg 2 DMAR:[DMA Read] Request device [06:00.0] fault addr 0 DMAR:[fault reason 06] PTE is the messages a critical ? and how i can fix them ?
*** Bug 624018 has been marked as a duplicate of this bug. ***
For the "no irq for vector" issue, try adding "pci=nomsi" to the kernel boot options. The DMAR messages are a completely different problem and should be solved by adding "intel_iommu=off" to the boot options. For common workarounds, see: http://fedoraproject.org/wiki/KernelCommonProblems
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.