Sponsored Content
Top Forums UNIX for Advanced & Expert Users hunting down for software interrupt causes Post 302365749 by marcpascual on Wednesday 28th of October 2009 02:43:59 AM
Old 10-28-2009
hunting down for software interrupt causes

Hi,

i have an rhel box with around 20 %soft every 2 seconds. The box is idle.
How do i start hunting down what's causing this? i believe /proc/interrupts is hardware related, procinfo is basically the same. where else can i look?

thanks,
Marc
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

timer interrupt

hello all since a process running in kernel mode cannnot be preempted by any other process what would be the status of Timer interrupt that occurs when the time quantum of a process is elapsed? thanks (2 Replies)
Discussion started by: compbug
2 Replies

2. HP-UX

Hunting Java memory. VSZ? 11.2 and 11.3

We are running into what appears to be a memory leak in java with a program that we are developing. The growth has been confirm on a 12day test. When we look at garbage collection with hpjtune, and jmeter, it appears to releasing the heap memory properly. Does anyone... (1 Reply)
Discussion started by: craigclee
1 Replies

3. Advertise with Us

Job Hunting in Uganda

Hello I am thinking of packing up and moving to Uganda if I can, especially if I can track down some UNIX/Linux type roles there. Broadband has just come ashore in Mombasa and should soon make its way through to UG, I think this is going to trigger a surge in expansion for what is currently a small... (0 Replies)
Discussion started by: steadyonabix
0 Replies

4. UNIX for Advanced & Expert Users

Interrupt storm detected on "irq 20" throttling interrupt source

I receive the following warning messages on a very new machine which has FreeBSD 8.1 x64 installed on it: Interrupt storm detected on "irq 20" throttling interrupt source It is unclear what this means and what its origins are (motherboard? CPU? RAM?). I can start the desktop and the message is... (4 Replies)
Discussion started by: figaro
4 Replies

5. UNIX for Advanced & Expert Users

Is there any shell command to show which interrupt handler handle which interrupt number?

Hi, all: Is there any shell command to show which interrupt handler handle which interrupt number in the system? li,kunlun (5 Replies)
Discussion started by: liklstar
5 Replies

6. What is on Your Mind?

Alarm interrupt and multithreading

Hi Friends any know how became a friend in this Android Programming Language (0 Replies)
Discussion started by: ljarun
0 Replies

7. What is on Your Mind?

Hunting Anomalous Bots - An Introduction to Cyber-Objects - Live From Cyberspace

https://www.unix.com/members/1-albums212-picture687.png Hunting Anomalous Bots - An Introduction to Cyber-Objects - Live From Cyberspace Click title image (above) for video tutorial. (5 Replies)
Discussion started by: Neo
5 Replies
LSDEV(8)							Linux System Manual							  LSDEV(8)

NAME
lsdev - display information about installed hardware SYNOPSIS
lsdev DESCRIPTION
lsdev gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels. OPTIONS
None. FILES
/proc/interrupts IRQ channels. /proc/ioports I/O memory addresses. /proc/dma DMA channels. BUGS
lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files sometimes use different names for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as `keyboard' in /proc/interrupts. This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example). The program does however try to match lines by stripping anything after a space or open parenthesis from the name, so that e.g. the `serial' lines from /proc/interrupts match the `serial(set)' lines from /proc/ioports. This attempt at DWIM might be considered a bug in itself. This program only shows the kernel's idea of what hardware is present, not what's actually physically available. SEE ALSO
procinfo(8). AUTHOR
Sander van Malssen <svm@kozmix.cistron.nl> 3rd Release 1998-05-31 LSDEV(8)
All times are GMT -4. The time now is 01:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy