Date: Fri, 18 Nov 2005 19:41:41 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Andrey Chernov <ache@freebsd.org> Cc: gnome@freebsd.org, current@freebsd.org Subject: Re: KSE: whom to blame, -current SMP or firefox? Message-ID: <1132360901.55741.9.camel@shumai.marcuscom.com> In-Reply-To: <20051118131131.GA96190@nagual.pp.ru> References: <20051118131131.GA96190@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-tBHKNuBYyDl8JGD3CtoI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-11-18 at 16:11 +0300, Andrey Chernov wrote: > The problem: I got 100% dead loop at 'install' stage of the 'firefox'=20 > port (after =3D=3D=3D> Building Chrome's registry... message). > '/usr/X11R6/lib/firefox/regchrome' is the program that loops (at the end=20 > of its task, so kill -9 continues install normally). That is SMP machine. >=20 > If I leave it for, say, 10mins, I start to get lots of=20 > calcru: runtime went backwards from 121010657 usec to 120993592 usec for=20 > pid 5769 (regchrome) > on my console. >=20 > The _same_ 'regchrome' binary & libs set runs without problem and exits=20 > quickly on another UP machine!!! Both machines are identical recent=20 > -current. >=20 > 'ktrace' shows that loop happens in KSE code. Here is relevant piece of=20 > 'kdump': > ... > 9152 regchrome NAMI "/usr/X11R6/lib/firefox/chrome/.reregchrome" > 9152 regchrome RET access -1 errno 2 No such file or directory > 9152 regchrome CALL write(0x6,0x282b8f8d,0x1) > 9152 regchrome GIO fd 6 wrote 1 byte > "8" > 9152 regchrome RET write 1 > 9152 regchrome CALL kse_release(0xbfbfe8a0) > 9152 regchrome RET kse_release 0 > 9152 regchrome CALL read(0x5,0xbf8fdb40,0x400) > 9152 regchrome GIO fd 5 read 1 byte > "8" > 9152 regchrome RET read 1 > 9152 regchrome CALL kse_release(0xbf8fdeb0) > 9152 regchrome RET kse_release 0 > 9152 regchrome CALL kse_release(0xbfbfe8a0) > 9152 regchrome RET kse_release 0 > 9152 regchrome CALL kse_release(0xbf8fdeb0) > 9152 regchrome RET kse_release 0 > 9152 regchrome CALL kse_release(0xbfbfe8a0) > 9152 regchrome RET kse_release 0 > 9152 regchrome CALL kse_release(0xbf8fdeb0) > 9152 regchrome RET kse_release 0 > ... loops ... >=20 > Any ideas? Could have to do with your CFLAGS. I certainly don't see this on my -CURRENT i386 machine using default CFLAGS (plus -g). That machine is a single CPU system with Hyperthreading enabled, so it looks like two CPUs. However, there may be a true SMP problem, but I don't think it's anything known to the FreeBSD GNOME team. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-tBHKNuBYyDl8JGD3CtoI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDfnTFb2iPiv4Uz4cRAoCBAKCPt2OzLPFAKSISgggThwbldCLD8gCfe26D wZSg+RKwvpNPHJaEbD+cBw0= =1Sw8 -----END PGP SIGNATURE----- --=-tBHKNuBYyDl8JGD3CtoI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1132360901.55741.9.camel>