Date: Tue, 16 Sep 2008 18:20:39 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Chitti Nimmagadda <Chitti.Nimmagadda@citrix.com> Cc: freebsd-bugs@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/127397: [amd64] 32bit application on FreeBSD-6.3 amd64 gets SIGBUS Message-ID: <20080916082039.GX15376@server.vk2pj.dyndns.org> In-Reply-To: <200809160254.m8G2sGnk006774@freefall.freebsd.org> References: <200809160254.m8G2sGnk006774@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--tuYRN1zEaS85jg/Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I can't quickly reproduce this on a roughly week old 6.4-PRERELEASE with a Turion64x2, though that system has been up for nearly 4 days. What else, if anything, is running on the system when it fails or doesn't fail? Does running lots of (especially large) processes before running your test reduce the likelihood of the failure occurring? Off the top of my head this looks like a race condition in the code that migrates i386 processes between CPUs - possibly a missing or misplaced memory barrier. Actually tracking this down is likely to be difficult. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --tuYRN1zEaS85jg/Y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjPbFcACgkQ/opHv/APuIdVtgCgwngCoUtqn0eo+eMwky6q2Xud 9IkAn2/CFsOf6j1cAe6QDIYD2Ch/X+ru =Jht8 -----END PGP SIGNATURE----- --tuYRN1zEaS85jg/Y--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080916082039.GX15376>