Re: Getting the name of a kernel thread?

2021-04-15 Thread Martin Husemann
On Thu, Apr 15, 2021 at 01:39:23PM -0700, Brian Buhrow wrote:
>   hello.  I just got two panics on a system running NetBSD-9.99.77/amd64. 
>  Unfortunately, I
> didn't have enough swap configured to capture a dump file.  However, I did 
> figure out that the
> problem is in  thread 6 of the kernel process, process 0.  However,  I am 
> having trouble
> figuring out what the name of thread 6  is.  Is there a key word I can use 
> with ps(1) to see
> the name of a particular thread?  I thought I might be able to do it with the 
> wchan field, but
> for this particular thread, the wchan field is "-".  If I can figure out what 
> thread 6 is on
> this system, it might give me a clue as to where the problem might be.  The 
> problem is hard to
> reproduce, so any data I can get from the running system would be helpful.

I'd use crash to get the "life" ddb experience:

> crash
crash> ps
PIDLID S CPU FLAGS   STRUCT LWP *   NAME WAIT
[..]
0   10 3   0   200  106ea84c0   nfssilly nfssilly
09 3   0   240  106ea8080 vdrain vdrain
08 3   0   240  106e979c0  modunload mod_unld
07 3   0   200  106e97580xcall/0 xcall
06 1   0   200  106e97140  softser/0
05 1   0   200  106e96d00  softclk/0
04 1   0   200  106e968c0  softbio/0
03 1   0   200  106e96480  softnet/0
02 1   0   201  106e96040 idle/0
00 3   0   2001c5e100swapper uvm

Martin


Getting the name of a kernel thread?

2021-04-15 Thread Brian Buhrow
hello.  I just got two panics on a system running NetBSD-9.99.77/amd64. 
 Unfortunately, I
didn't have enough swap configured to capture a dump file.  However, I did 
figure out that the
problem is in  thread 6 of the kernel process, process 0.  However,  I am 
having trouble
figuring out what the name of thread 6  is.  Is there a key word I can use with 
ps(1) to see
the name of a particular thread?  I thought I might be able to do it with the 
wchan field, but
for this particular thread, the wchan field is "-".  If I can figure out what 
thread 6 is on
this system, it might give me a clue as to where the problem might be.  The 
problem is hard to
reproduce, so any data I can get from the running system would be helpful.

-thanks
-Brian