Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Jan 2011 16:46:12 +0200
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Beat G?tzi <beat@chruetertee.ch>
Cc:        current@freebsd.org
Subject:   Re: Running linux ldconfig on tmpfs results in unkillable process
Message-ID:  <20110118144611.GP2518@deviant.kiev.zoral.com.ua>
In-Reply-To: <4D35A0BB.3010601@chruetertee.ch>
References:  <4D35A0BB.3010601@chruetertee.ch>

next in thread | previous in thread | raw e-mail | index | archive | help

--tB3UQx9o7itSJcWB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 18, 2011 at 03:16:27PM +0100, Beat G?tzi wrote:
> Hi,
>=20
> I've a tinderbox which uses tmpfs to build ports. Every time I build a
> port which executes linux ldconfig it results in an unkillable process
> which uses 100% CPU. The problem is reproduceable without tinderbox:
>=20
> # uname -a
> FreeBSD daedalus.network.local 9.0-CURRENT FreeBSD 9.0-CURRENT #3
> r216761: Tue Dec 28 15:32:26 CET 2010
> root@daedalus.network.local:/usr/obj/usr/src/sys/GENERIC  i386
> # mkdir /compat/test
> # mount -t tmpfs tmpfs /compat/test
> # cp -Rp /compat/linux/* /compat/test/
> # mount -t linprocfs linprocfs /compat/test/proc
> # /compat/linux/sbin/ldconfig -r /compat/test/
> # pgrep ldconfig
> 3449
> # procstat -i 3449 | grep KILL
>  3449 ldconfig         KILL     ---
> # kill -9 3449
> # procstat -i 3449 | grep KILL
>  3449 ldconfig         KILL     P--
>=20
> >From top(1):
> PID USERNAME THR PRI NICE  SIZE   RES STATE    C  TIME   WCPU COMMAND
> 3449 root     1  44    0   992K   712K CPU1    1  10:06 100.00% ldconfig
>=20
> When I reboot the machine it hangs after "All buffers synced.".
>=20
> I've uploaded some additional output of procstat and ktrace here:
> http://people.freebsd.org/~beat/logs/linux-ldconfig-tmpfs.txt
>=20
> Anyone knows how to fix this?
kdump for the trace of the linux binary is a garbage. You need to
use linux_kdump (from ports).

I think that your process is looping in the kernel, you can confirm this
by dropping in the ddb and doing "bt <pid>".

--tB3UQx9o7itSJcWB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk01p7MACgkQC3+MBN1Mb4ibqQCeIWbm3HkyTJzfItl0a8belSq3
yFsAoJbFfZTTdEg1CXOM/FVgNIzaja0h
=OVew
-----END PGP SIGNATURE-----

--tB3UQx9o7itSJcWB--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110118144611.GP2518>