RHEL 6.4 Error - kernel:do_IRQ: 1.205 No irq handler for vector (irq -1)

I have a RHEL 6.4 workstation with a HW RAID 0 drive that is mounted to another 6.4 workstation. I am recieving kernel:do_IRQ: 1.205 No irq handler for vector (irq -1) on the machines with the drive that has the local HW RAID 0 drive. The other machine that has the drive mounted does not have this error message.

Not sure if this info makes any difference or not, but I did have a hit on Google yesterday about this error and the syncing of a RAID drive.

More simply stated I have a kernel:do_IRQ: 1.205 No irq handler for vector (irq -1) error and do not have a clue what to look at to get rid of it.

All help greatly appreciated!!
capperdog13Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SandyCommented:
did you checked the array status  from BIOS ?

TY/SA
0
capperdog13Author Commented:
I did not... I was about to boot into the RAID Bios and noticed I am getting the same message on the other workstation that too has a HW RAID 0 array.

The only thing that has changed in the last day or two is the number of people starting to use these two machines.
0
Seth SimmonsSr. Systems AdministratorCommented:
wondered if it's HP systems
we had this on ours and updated the BIOS
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

capperdog13Author Commented:
The two workstations are HP Z800's.
0
Seth SimmonsSr. Systems AdministratorCommented:
have you looked at the BIOS at all in terms of a newer version?
0
capperdog13Author Commented:
I am actually checking that now. I do believe these two machines do not have the latest bios from HP... That being said... I am a newb to Linux. I know enough to be dangerous and Googling bios update in Linux looks tricky.

Last thing I wantto do is is kill these machiens they are partially in production. Can you provide instruction for updating the bios on a HP?
0
capperdog13Author Commented:
Rockin! Thank you sir.
0
capperdog13Author Commented:
Bios updated... PDF did not help much with hp-lxbios app... Just did it old school. Will let it ride over night and see if the errors persist.

Thanks!
0
capperdog13Author Commented:
So far so good with the bios update. A little hesitant to say we have it cornered at the moment as not many people have used these machines in the last 16 hours.

Will keep this one open for now and update accordingly.
0
capperdog13Author Commented:
It's back. I found something about disabling Interupt Remapping in the bios as a fix. This was from RH support. On these HP Z800's this is not in the bios at least what i can see of it. Found another article about the chipset istself that mentioned disabling Interupt Remapping fro various reasons and detailed instruction of how it is done. Not going to happen in the HP bios. In that same post what was causing the issues dealt with VT-d. I did not find VT-d in the bios but did find VT-d2 and went ahead and disabled this feature.

We'll see what happens. If you're familiar with getting deeper into the HP bios please let me know.
Thanks!
0
capperdog13Author Commented:
Well... After about 24 hours disabling VT-d2 seems to have fixed the problem. No errors thus far.

Will continue to monitor the machines and repost if this starts happening again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
yes i think you nailed it

check out #52 on page 25

http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf

Red Hat addresses this also

https://access.redhat.com/site/solutions/110053

not sure if you have either of these chipsets but seems the description and symptoms are what you experience
0
capperdog13Author Commented:
Thanks again to SA and thanks to Seth for input on this issue. Both of these experts got me pointed in the right direction to a solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.