swiftgri...@gmail.com (Swift Griggs) writes:
>Next time it happens, I'll pay attention and expand the kernel threads to
>see which one is doing it. I guess there is no way to do a gdb 'attach' to
>the kernel thread to get a backtrace, though. I'm assuming one has to do
>this sort of thing with
On Tue, 4 Oct 2016, Michael van Elst wrote:
> [system] is all the kernel threads. In top you can switch to thread
> display and get more details. Kernel threads are also displayd with 'ps
> -s' and you can augment the display with the thread name using '-o
> lname'.
Ah, I should have known ther
swiftgri...@gmail.com (Swift Griggs) writes:
>Folks, I recently installed NetBSD on a Lenovo M83 Tiny machine and from
>time to time, I notice the "[system]" (appears to be a kernel thread?)
>getting up to 80% of the CPU while the box is doing nothing.
[system] is all the kernel threads. I
On 03/10/2016 19:35, Swift Griggs wrote:
Folks, I recently installed NetBSD on a Lenovo M83 Tiny machine and from
time to time, I notice the "[system]" (appears to be a kernel thread?)
getting up to 80% of the CPU while the box is doing nothing. No
processes are active and a reboot clears t
Folks, I recently installed NetBSD on a Lenovo M83 Tiny machine and from
time to time, I notice the "[system]" (appears to be a kernel thread?)
getting up to 80% of the CPU while the box is doing nothing. No
processes are active and a reboot clears the issue (except when it
doesn't. I pow
