Re: runaway intr problems: powerd and/or hw.acpi.cpu.cx_lowest related

On 08/22/2010 23:20, Andriy Gapon wrote:
> on 23/08/2010 06:17 Doug Barton said the following:
>
>> http://people.freebsd.org/~dougb/intr-out-3.txt
>
> So, hm, npviewer.bin eats all the CPU time?

No, the odd bits of that one are the fact that the intr threads irq17, 
irq256, and irq20; are showing up at all, and/or showing up with more 
than a fraction of a percent of cpu time. Usually they don't, and the 
fact that they did at that point in time was indicative of the fact that 
the "runaway intr" problem was happening. _Incidentally_ npviewer.bin 
was taking up more cpu than it usually does, but I think that's another 
symptom of the underlying problem.

Here is a typical, non-problematic top output while running a flash video:

last pid: 10841;  load averages:  0.22,  0.12,  0.19    up 0+04:15:49 
23:46:11
171 processes: 3 running, 148 sleeping, 20 waiting
CPU 0: 14.8% user,  0.0% nice,  3.1% system,  0.0% interrupt, 82.0% idle
CPU 1: 18.8% user,  0.0% nice,  0.0% system,  0.0% interrupt, 81.3% idle
Mem: 342M Active, 1397M Inact, 168M Wired, 49M Cache, 112M Buf, 45M Free
Swap: 1024M Total, 1444K Used, 1022M Free

   PID USERNAME   PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
    10 root       171 ki31     0K    16K CPU0    0 203:29 82.86% {idle: 
cpu0}
    10 root       171 ki31     0K    16K RUN     1 191:24 81.05% {idle: 
cpu1}
10813 dougb       54    0   420M 78196K select  0   0:18 17.77% npviewer.bin
10822 dougb       47    0   420M 78196K futex   1   0:05  6.30% npviewer.bin
10839 dougb       45    0   420M 78196K futex   1   0:03  3.66% npviewer.bin
10840 dougb       45    0   420M 78196K futex   1   0:03  3.66% npviewer.bin
10832 dougb       45    0   420M 78196K pcmwrv  1   0:03  2.88% npviewer.bin
  1598 dougb       44    0   163M   142M select  1  12:06  1.56% Xorg
    11 root       -68    -     0K   160K WAIT    1   1:10  0.49% {irq17: 
wpi0}
10770 dougb       44    0   178M   136M ucond   0   0:00  0.39% 
{firefox-bin}
10770 dougb       45    0   178M   136M select  1   0:15  0.29% {initial 
thread
    11 root       -80    -     0K   160K WAIT    0   0:45  0.10% 
{irq256: hdac0}

I really wish people would stop focusing on flash here. :)  It's simply 
the easiest and most consistent way that I have triggered this problem, 
it's not the only one.


Doug

-- 

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/

	Computers are useless. They can only give you answers.
			-- Pablo Picasso