chroot: conftest stuck in umtxn state

[Erik Cederstrand]

Erik Cederstrand wrote:
> Hi!
> 
> I'm installing some ports into a chroot environment that will eventually 
> go on a separate machine. When installing python25, the installation 
> gets stuck in the configure phase when checking for pthread:
> 
> # chroot /perfmon/slaves/src/packages/CURRENT-2007.11.27.13.29.20/ 
> /bin/sh -c "cd /usr/ports/lang/python25; WRKDIRPREFIX=/tmp make 
> BATCH=yes install clean; "
> [...]
> checking whether cc accepts -Olimit 1500... no
> checking whether pthreads are available without options... no
> checking whether cc accepts -Kpthread... no
> checking whether cc accepts -Kthread... no
> checking whether cc accepts -pthread...
> 
> 
> and then the installation freezes. top shows conftest is in umtx state:
> 
>  1696 root        1  96    0  3200K   840K umtxn    0:00  0.00% conftest
> 
> 
> and is only killable with kill -9. /usr/ports in the chroot is 
> nullfs-mounted, and ports options files have been pre-installed in the 
> chroot's /var/db/ports
> 
> The host:
> # uname -a
> FreeBSD perfmonserver.itu.dk 7.0-BETA4 FreeBSD 7.0-BETA4 #1: Mon Dec  3 
> 16:15:35 CET 2007 
> root at perfmonserver.itu.dk:/usr/obj/usr/src/sys/PERFMONSERVER  i386
> 
> The chroot contains CURRENT from various dates, in this case 
> 2007.11.27.13.29.20. It is compiled with this src.conf (and no other 
> config modifications):
> 
> WITHOUT_ATM= true
> WITHOUT_AUDIT= true
> WITHOUT_AUTHPF= true
> WITHOUT_BIND= true
> WITHOUT_BLUETOOTH= true
> WITHOUT_CALENDAR= true
> WITHOUT_CDDL= true
> WITHOUT_CVS= true
> WITHOUT_DICT= true
> WITHOUT_EXAMPLES= true
> WITHOUT_FORTRAN= true
> WITHOUT_GAMES= true
> WITHOUT_GPIB= true
> WITHOUT_HTML= true
> WITHOUT_I4B= true
> WITHOUT_IPFILTER= true
> WITHOUT_IPX= true
> WITHOUT_LPR= true
> WITHOUT_MAN= true
> WITHOUT_PF= true
> WITHOUT_RESCUE= true
> WITHOUT_SENDMAIL= true
> WITHOUT_SHAREDOCS= true
> WITHOUT_USB= true
> 
> 
> If I try to install python25 on the host, this problem does not occur.
> 
> Any debugging help would be greatly appreciated.

I should have done a more thorough googling. It seems this problem was 
fixed that same day. Rebuilding now, and will return if the problem 
persists.

Erik