Date: Wed, 15 Apr 2009 15:02:49 +0300 From: "Oleg V. Nauman" <oleg@opentransfer.com> To: Ronald Klop <ronald-freebsd8@www.klop.ws> Cc: freebsd-stable@freebsd.org Subject: Re: 7.2-PRERELEASE: make process waiting indefinitely Message-ID: <20090415150249.19ecof1i8gkos8kg@webmail.opentransfer.com> In-Reply-To: <op.use7yoh38527sy@82-170-177-25.ip.telfort.nl> References: <20090414160411.042472seockg0css@webmail.opentransfer.com> <op.use7yoh38527sy@82-170-177-25.ip.telfort.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Ronald Klop <ronald-freebsd8@klop.yi.org>: > On Tue, 14 Apr 2009 15:04:11 +0200, Oleg V. Nauman > <oleg@opentransfer.com> wrote: > >> >> Have experienced today strange issue with my fresh RELENG_7 ( =20 >> sources from yesterday April 13, userland and kernel in sync ) - =20 >> sometimes some processes stop running without any visible reason. =20 >> Have seen it twice today during KDE compilation - make process just =20 >> waiting for something while nothing else compiles or some other =20 >> way prevents this process from running ( no SIGSTOP performed, no =20 >> Ctrl-S performed on console). Well it possible related to ( or =20 >> triggered by ) new ports compilation feature for SMP machines ( =20 >> most of KDE port marked as MAKE_JOBS_SAFE=3Dyes ) but anyway this =20 >> stuck process behavior is strange. kill -SIGCONT not helps, but it =20 >> killable ( Ctrl-C helps at least ) >> Well some info related to this process: >> procstat -t 63472 output: >> >> PID TID COMM TDNAME CPU PRI STATE WCHAN >> 63472 100059 make - 1 92 sleep wait >> >> procstat -kk 63472 output: >> >> PID TID COMM TDNAME KSTACK >> 63472 100059 make - mi_switch+0x2c8 =20 >> sleepq_switch+0xd9 sleepq_catch_signals+0x239 sleepq_wait_sig+0x14 =20 >> _sleep+0x307 kern_wait+0xa36 wait4+0x3b syscall+0x2b3 =20 >> Xint0x80_syscall+0x20 >> >> Some related sysctls output: >> >> kern.smp.cpus: 2 >> kern.smp.disabled: 0 >> kern.smp.active: 1 >> >> uname -msr output: >> FreeBSD 7.2-PRERELEASE i386 > > It sounds like > http://www.mail-archive.com/freebsd-stable@freebsd.org/msg102628.html . > There are some tips in that mailthread about debugging it. Thank you. Looks like it was the same issue. > > Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090415150249.19ecof1i8gkos8kg>