Re: Any ideas why this kernel thread is going nuts?

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Oct 25, 2016 at 03:49:32PM -0600, Swift Griggs wrote:
> 
> I read the xcall(9) man page, but I still don't see why this kernel thread
> should be taking this much CPU time. It'll go on like this for 30-60 minutes
> and I can kill every app I'm running - no change. The main reason I know
> it's happening is that I hear the CPU fan spin up. I can't coorelate this to
> any activity I'm starting or stopping. I've only experienced this with the
> i386 port on 7.0.1.
> 
> This is related to me asking the ignorant questions about how to see kernel
> threads and several folks reminded me to either use ps with options or top
> with 't'. Here's the 'top' view with threads expanded:
> 
>   PID   LID USERNAME PRI STATE      TIME   WCPU    CPU NAME      COMMAND
>     0    34 root     127 xcall/3   89:50 22.71% 22.71% xcall/3   [system]
>     0    68 root     126 RUN/3    223:24 11.43% 11.43% pgdaemon  [system]
>     0    28 root     127 xcall/2   81:43 10.16% 10.16% xcall/2   [system]
>     0    22 root     127 xcall/1   60:01  1.17%  1.17% xcall/1   [system]
>     0     7 root     127 xcall/0   63:15  0.63%  0.63% xcall/0   [system]

I'd say the problem are not the xcall threads but the page daemon.
The page daemon probably does a lot of cross-calls for its work.

Now you'd need to look at memory usage to see why the pagedaemon is working
so much.


-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--