Date: Sat, 22 Apr 2006 13:58:32 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Sean Winn <sean@gothic.net.au> Cc: 'Daniel Eischen' <deischen@freebsd.org>, freebsd-threads@freebsd.org, freebsd-sparc64@freebsd.org, 'Kris Kennaway' <kris@obsecurity.org> Subject: Re: pthread_mutex_timedlock on sparc64 Message-ID: <20060422175832.GA14305@xor.obsecurity.org> In-Reply-To: <002301c665d8$72f3a7f0$2522630a@t22> References: <001801c66372$a032e770$2522630a@t22> <002301c665d8$72f3a7f0$2522630a@t22>
next in thread | previous in thread | raw e-mail | index | archive | help
--gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 22, 2006 at 04:46:13PM +1000, Sean Winn wrote: > owner-freebsd-sparc64@freebsd.org wrote: > > Kris Kennaway wrote: > >> On Tue, Apr 18, 2006 at 07:28:00PM +1000, Sean Winn wrote: > >>> owner-freebsd-sparc64@freebsd.org wrote: > >>>>=20 > >>>> libthr *is* the thread library on sparc64; as Daniel says, > >>>> libpthread is not ported to sparc64. > >>>>=20 > >>>> Kris > >>>=20 > >>> Not yet in 6.x > >>>=20 > >>> 19:25 Tue 18-Apr sean@bloody [~] uname -msr > >>> FreeBSD 6.1-RC1 sparc64 > >>> 19:25 Tue 18-Apr sean@bloody [~] ls -l /usr/lib/libpthread.so > >>> lrwxrwxrwx 1 root wheel 9 Apr 17 04:05 /usr/lib/libpthread.so -> > >>> libc_r.so > >>=20 > >> Oops, I forgot about that..although so did David when he removed > >> libc_r from 7.0 and broke sparc :-) > >>=20 > >> So I guess this is a libc_r missing feature. Probably the solution > >> is to use libthr on 6.x too (I don't know if it works well enough on > >> 5.x). libthr causes witness panics under load on sparc64 though. > >>=20 > >> Kris > >=20 > > Would threading problems be related to sparc64/73413? I've noticed it > > sitting idle for a long while, and the test case still core dumps. The > > PR it references (sparc64/72998) also is open. > >=20 > >=20 >=20 > And as a followup to these two PRs - the patches apply cleanly to 6.1RC1 > and the test case in the PR certainly doesn't core dump anymore. Thanks. > Using mysqld 4.1.18 with super-smack update-select has had no panics or > core dumps after these changes with both libkse and libthr; all that > means of course is that it doesn't introduce something horribly wrong, > not that it works - is there some regression test for threading? >=20 > Note: all my testing is done on a single CPU AXi. Hmm, just to confirm, you were seeing core dumps with super-smack before you applied the changes? Because I have run that extensively on MP sparc machines without issues. Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFESm7IWry0BWjoQKURAnjkAKDXZLbd55HiKfN0Q/WDbbxMOaAIngCg9sCj EqsZVO+Fiy413KMomuqX094= =v1Qd -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060422175832.GA14305>