Date: Sun, 31 Oct 2010 16:05:00 -0700 From: Garrett Cooper <gcooper@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Cc: hackers@freebsd.org Subject: Re: ccache pausing in buildworld Message-ID: <AANLkTi=yxpZ_1whFJ4OvkMbmv9%2BnzkHc43D1Ezs5WRM1@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1010311019150.9437@wonkity.com> References: <alpine.BSF.2.00.1010311019150.9437@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 31, 2010 at 9:38 AM, Warren Block <wblock@wonkity.com> wrote:
> About a month ago, ccache began to pause in buildworld. =A0The build does=
n't
> halt or quit, it stays running but not doing anything:
>
> /usr/local/libexec/ccache/world-cc -fpic -DPIC -O2 -pipe -march=3Dprescot=
t
> -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include
> -I/usr/src/lib/libc/i386-DNLS -D__DBINTERFACE_PRIVATE
> -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/li=
bc
> -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE
> -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN
> -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=3Dgnu9=
9
> -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k
> -Wno-uninitialized -Wno-pointer-sign -c crypt_xdr.c -o crypt_xdr.So
>
> And there it stays:
>
> =A0load: 0.02 =A0cmd: make 83143 [select] 401.32r 0.05u 0.05s 0% 852k
> =A0load: 0.01 =A0cmd: make 83143 [select] 409.08r 0.05u 0.05s 0% 852k
> =A0load: 0.01 =A0cmd: make 83143 [select] 422.00r 0.05u 0.05s 0% 852k
>
> The file where it pauses varies depending on the number of jobs (-j) opti=
on.
> =A0The example above is with -j6; -j1 doesn't fix it, although it pauses =
on
> nslexer.c instead.
>
> This is on 8-stable as of today, i386. =A0The -march=3Dprescott option co=
mes
> from CPUTYPE?=3Dcore2 in make.conf, and removing that setting doesn't fix=
the
> problem.
>
> buildworld without ccache works fine, just takes more than twice as long.
>
> The kernel target works fine with or without ccache.
>
> Any ideas?
Have you tried trussing or ktrace'ing the processes to determine
where they get stuck?
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=yxpZ_1whFJ4OvkMbmv9%2BnzkHc43D1Ezs5WRM1>