Subject: Process stuck on exit
To: None <current-users@NetBSD.ORG>
From: None <martin@netbsd.org>
List: current-users
Date: 10/31/2001 11:26:49
I'm using a -current system (updated yesterday) with a kernel from
the i386 SMP branch on a dual PII system.
While doing "make build" I saw make get stuck twice, once two or three
weeks ago, the second time yesterday. Looks like some process finishes,
and gets stuck on exit, in this case as (pid 5341):
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
205 270 267 7 18 0 1096 4 pause IWs p1 0:00.00 -csh (tcsh)
0 271 270 0 18 0 1136 692 pause S p1 0:00.08 -tcsh
0 5286 28039 0 10 0 464 372 wait S+ p1 0:00.00 /bin/sh -ec targ=dependall;dir=lpr;\t\t case "$dir" in /*)\t\t\t\t\t\t ec
0 5287 5286 0 10 0 328 856 wait S+ p1 0:00.05 make _THISDIR_ usr.sbin/lpr/
0 5288 5287 0 10 0 464 372 wait S+ p1 0:00.01 /bin/sh -ec targ=dependall;dir=common_source;\t\t case "$dir" in /*)\t\t\
0 5289 5288 0 10 0 344 880 wait S+ p1 0:00.05 make _THISDIR_ usr.sbin/lpr/common_source/
0 5310 5289 0 10 0 460 368 wait S+ p1 0:00.00 /bin/sh -ec cd /usr/src/usr.sbin/lpr/common_source; make realall
0 5311 5310 0 10 0 436 972 wait S+ p1 0:00.07 make realall
0 5338 5311 29 10 0 124 644 wait S+ p1 0:00.01 /usr/tools/bin/i386--netbsdelf-gcc -O2 -pipe -Wall -Wstrict-prototypes -W
0 5341 5338 29 57 0 0 0 - Z+ p1 0:00.00 (as)
0 9354 14939 0 10 0 376 4 wait S+ p1 0:00.08 make -m /usr/src/share/mk dependall
0 14934 271 0 10 0 376 4 wait S+ p1 0:00.07 make build
0 14939 14934 0 10 0 428 4 wait S+ p1 0:00.08 make -m /usr/src/share/mk cleandir do-make-tools do-distrib-dirs includes
0 28038 9354 0 10 0 464 4 wait S+ p1 0:00.01 /bin/sh -ec targ=dependall;dir=usr.sbin;\t\t case "$dir" in /*)\t\t\t\t\t
0 28039 28038 0 10 0 1304 800 wait S+ p1 0:00.39 make _THISDIR_ usr.sbin/
The system worked fine otherwise, I could open new terminal windows and
kill the parent process, which stopped make as well. Everything continued
without noticable problem. I restarted the build and it finished.
Anyone have good ideas what may cause this? I'll attach a serial console and
run a LOCKDEBUG kernel if that will help to find the cause of this.
Martin