HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: spurious interrupt message
Operating System - Linux
1825931
Members
2836
Online
109689
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 01:43 PM
01-29-2003 01:43 PM
spurious interrupt message
Does any one know what this mean, "spurious interrupt 8259A interrupt: IRQ7". What device is the system yakking about? Any suggestion? Thanks.
Reputation of a thousand years can be determined by the conduct of an hour
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 01:55 PM
01-29-2003 01:55 PM
Re: spurious interrupt message
maybe this helps,
http://www7.informatik.uni-erlangen.de/~ksjh/research/cluster/timesync/sprint.html
Robert-Jan.
http://www7.informatik.uni-erlangen.de/~ksjh/research/cluster/timesync/sprint.html
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 02:36 PM
01-29-2003 02:36 PM
Re: spurious interrupt message
This is on AMD athon CPU and running RH7.3 with a compiled kernel version of 2.4.20; default kernel that came with redhat 7.3 is running ok; why does the new kernel yak about this spurious interrupt message? Any idea? Thanks.
Reputation of a thousand years can be determined by the conduct of an hour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2003 03:56 PM
01-29-2003 03:56 PM
Re: spurious interrupt message
Sometimes debugging messages make it through the release cycle.
Other times it's an obscure branch of code which in 'normal operation' wouldn't get reached, but some misclaneous piece of hardware causes code to go down there.
It's a common enough occurance for the diverse range of developers that maintain the kernel source tree.
Since the people who maintain the release cycle might not have the exact piece of hardware which aggrivates the message to show up, these things slip though.
Recent example is with Compaq ML330's on-board SCSI controller and RH7.3 displayed a imilar message.
I don't beleive it's anything to be concerned about, so short of modifying kernel source code yourself (you feel up to that?), just ignore it.
Other times it's an obscure branch of code which in 'normal operation' wouldn't get reached, but some misclaneous piece of hardware causes code to go down there.
It's a common enough occurance for the diverse range of developers that maintain the kernel source tree.
Since the people who maintain the release cycle might not have the exact piece of hardware which aggrivates the message to show up, these things slip though.
Recent example is with Compaq ML330's on-board SCSI controller and RH7.3 displayed a imilar message.
I don't beleive it's anything to be concerned about, so short of modifying kernel source code yourself (you feel up to that?), just ignore it.
One long-haired git at your service...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP