On Mon, 2005-08-01 at 14:20 -0700, Daniel Walker wrote:
> It means that IRQ 14 is running for a long time as an RT task
Oh yeah, I forgot to comment on this. Yes IRQ 14 is rather slow. It's
the IDE drive interrupt and it gets pretty busy. Actually the check
doesn't really see if it is running for a long time, since it gets
scheduled out. But I'm running this on a slow 368MHz machine and it
takes some time. There's cases where every second the interrupt just
happened to be running, since that is what it checks. It doesn't check
to see if the thread actual sleeps.
I may add something to your patch to see if a thread actually goes to
sleep. If it doesn't then to flag it as possible stuck.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |