LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > General
User Name
Password
General This forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!

Notices



Reply
 
Search this Thread
Old 04-02-2013, 10:11 PM   #1
andy713
Member
 
Registered: Sep 2009
Location: Louisiana
Distribution: Slackware64-14
Posts: 38

Rep: Reputation: 0
Interrupts on a laptop


So, my wife's HP laptop has a problem that is causing it to generate >4000 interrupts per second and chew up the CPU. Problem is it is running Window 7. Now before you go off about this being a Slackware forum, let's be honest. Normally I would open a shell and cat /proc/interrupts, wait a few seconds, do it again, and I'd know what the problem was. Unfortunately, this doesn't appear to be something that Windoze knows how to do. Why do I ask this here? Because we all know that I'd spend all my waking hours trying to explain the problem on some MS forum to a legion of clueless "experts", when we all know that as much as we don't like it, we live in a Windoze world and we have probably forgotten more about Windoze than most of the so-called experts know. The saying goes that if you have a computer question ask a Slacker, and I'm hoping that someone here knows.

Please don't reply with disparaging comments about Windows; you're preaching to the choir. We're all thinking it. And you probably couldn't dislike it more than me without spontaneously bursting into flame anyway. http://www.despair.com/burnout.html

Andy
 
Old 04-02-2013, 11:53 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 876

Rep: Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826
Can you test with -current to see if the problem still exists?
 
Old 04-02-2013, 11:57 PM   #3
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware [64]X{.0|.1|.2|-current} ::X>=12<=14, FreeBSD_10{.0|.1}
Posts: 2,179

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
Cool

Quote:
Originally Posted by volkerdi View Post
Can you test with -current to see if the problem still exists?
;-)
 
Old 04-03-2013, 03:43 AM   #4
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Post the output of '/proc/interrupts', and '/sbin/lspci -k'.
 
Old 04-03-2013, 08:32 AM   #5
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12 and higher
Posts: 229

Rep: Reputation: 51
Slacker by night, Windows programmer in ArcGIS environment by day.

Go to http://www.sysinternals.com and download the "sysinternals suite". My first tool of choice is "procexp", the process explorer. Gives you a configurable htop-like display of what is going on, complete with sortable columns like %CPU, etc. By the way, the URL I have redirects to MSDN, the Microsoft Developer Network, and is Microsoft-hosted. Mark Russinovich was hired by MS on the strength of his Sysinternals stuff.

I also use "autoruns" quite a bit, it shows all of the eleventy-seven locations that Windows stuff can automatically run from as well as letting you toggle the running on and off. Be careful here, other utilities do the same thing but don't necessarily understand just where autoruns stuffs the items you've turned off.

After you've identified some process that is _responding_ to lots of interrupts you might want to trace exactly what the process is doing by using "procmon", the process monitor. You can build filters in procmon so that you can narrow down the monitoring from all windows events/registry writes/disk reads to just the few (or the many, or the specific process) that you want to monitor.

Procexp also has a "trace-the-boot" mode where it gets started really early and logs the boot process.

Hope this helps.

EDIT: Add some columns in Procexp, you'll probably be able to figure out what, but things like Disk I/O, swap space, memory used, etc. You might just be having a case of not quite enough RAM and thrashing the pagefile like crazy. If you do Disk I/O be sure to add all three (reads, writes, other, IIRC).

Last edited by jamesf; 04-03-2013 at 08:34 AM. Reason: additional info
 
Old 04-03-2013, 09:53 AM   #6
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12 and higher
Posts: 229

Rep: Reputation: 51
Another thing - googling combinations of 'sysinternals interrupts' brings up some google search suggestions as well as some interesting ideas.
 
Old 04-07-2013, 07:47 PM   #7
andy713
Member
 
Registered: Sep 2009
Location: Louisiana
Distribution: Slackware64-14
Posts: 38

Original Poster
Rep: Reputation: 0
I tried procexp but it only tells me what I already know, that the CPU is churing at 10% servicing some interrupt. The closest thing I've found to help was on the MS site, which suggests I look at the times of the drivers and guess that the driver handling the interrupt will tell me what hardware is the problem. The other problem is that this of course goes away if I reboot, only to eventually come back. Is it any wonder Linus thought he could do better?

Andy
 
Old 04-07-2013, 09:38 PM   #8
michaelk
Moderator
 
Registered: Aug 2002
Posts: 12,163

Rep: Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784Reputation: 784
Moved: This thread is more suitable in Non-*NIX>General and has been moved accordingly to help your thread/question get the exposure it deserves.
 
Old 04-08-2013, 10:46 AM   #9
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12 and higher
Posts: 229

Rep: Reputation: 51
This is in no way an endorsement of any of the suggestions of the linked thread:
http://www.msfn.org/board/topic/1402...dpc-interrupt/

There are some good ideas there, though.

Basically you're down to tracking it down via finding the process where all the time is going, determining what that process (or thread) does, and fixing it.

Yeah, I know...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Interrupts elico Linux - Newbie 1 04-10-2012 03:55 PM
Interrupts elico Linux - Newbie 1 02-20-2012 03:21 AM
Can anyone please explain about "Function call interrupts" entry in /proc/interrupts? cyclops.xmen Linux - Software 2 12-09-2009 01:13 PM
Interrupts mrchsreddy Linux - Newbie 2 11-18-2008 07:27 PM
Interrupts rhcohen Programming 0 01-22-2001 03:30 PM


All times are GMT -5. The time now is 08:17 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration