Re: too many warning messages from gnumach

[Samuel Thibault]

Da Zheng, le Wed 17 Mar 2010 17:39:55 +0800, a écrit :
> On 10-3-17 下午5:20, Samuel Thibault wrote:
> > Da Zheng, le Wed 17 Mar 2010 10:25:13 +0800, a écrit :
> >>  0:        1fef5234        1fef3294        8               0               
> >> 12              gnumach
> >>     0:(...)        1:(...) ...
> >>  1:        1fef6b24        1fef6bc4        628             0               
> >> 12
> >>    ...
> >> ...
> >>
> >> We can see that the first task is gnumach, which has 8 threads, and it 
> >> lists all
> >> threads of gnumach at the end. But I don't know some columns such as
> >> SUS(suspend?) and PR (priority?).
> >> But the command doesn't always display the command of a task. For example, 
> >> the
> >> next task has 628 threads, but I don't know which process it corresponds 
> >> to.
> > 
> > It's task number 1, so it's ext2fs. The fact that it has a huge lot of
> > threads also hints me that :)
> Maybe ext2fs is heavily used during booting, so it created many threads to
> handle requests.

Not only at boot. Think about commands like find . -name foo which
actually trigger a huge lot of requests.

> > For the record, here are the initial tasks and their pid:
> > 
> > task 0 pid 2: gnumach
> > task 1 pid 3: ext2fs
> > task 2 pid 4: exec
> > task 3 pid 1: init
> > task 4 pid 0: proc
> > task 5 pid 5: auth
> > task 6 pid 6: /bin/bash
> OK, so the task that triggers the warning is exec during login. How do you get
> the mapping between task ID and pid?

Well, task 0, 1, 2, 3, 4 and 5 are clearly gnumach, ext2fs, exec, init,
proc and auth, just read the usual boot log :) Then just run ps to know
which PID they have.

samuel