Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2014-02-26
14
Medium Priority
?
1,845 Views
Last Modified: 2014-03-05
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!!
0
Comment
Question by:capperdog13
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 9
  • 4
14 Comments
 
LVL 13

Assisted Solution

by:Sandy
Sandy earned 300 total points
ID: 39889380
did you checked the array status  from BIOS ?

TY/SA
0
 

Author Comment

by:capperdog13
ID: 39889405
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
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 39889787
wondered if it's HP systems
we had this on ours and updated the BIOS
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:capperdog13
ID: 39889902
The two workstations are HP Z800's.
0
 
LVL 35

Assisted Solution

by:Seth Simmons
Seth Simmons earned 600 total points
ID: 39889963
have you looked at the BIOS at all in terms of a newer version?
0
 

Author Comment

by:capperdog13
ID: 39889984
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
 

Author Comment

by:capperdog13
ID: 39890009
Rockin! Thank you sir.
0
 

Author Comment

by:capperdog13
ID: 39890523
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
 

Author Comment

by:capperdog13
ID: 39892264
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
 

Author Comment

by:capperdog13
ID: 39892508
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
 

Accepted Solution

by:
capperdog13 earned 0 total points
ID: 39894882
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
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 39895151
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
 

Author Closing Comment

by:capperdog13
ID: 39905910
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

Featured Post

Quick Start: DOCKER

Sometimes you just need a Quick Start on a topic in order to begin using it.. this is just what you need to know to get up and running with Docker!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
Fine Tune your automatic Updates for Ubuntu / Debian
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Suggested Courses

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question