Date: Sat, 5 Jun 2004 12:51:22 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Tim Robbins <tim@robbins.dropbear.id.au> Cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE Message-ID: <Pine.GSO.4.10.10406051236030.14185-100000@pcnet5.pcnet.com> In-Reply-To: <20040605163123.GA29935@cat.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Jun 2004, Tim Robbins wrote: > On Sat, Jun 05, 2004 at 12:06:01PM -0400, Daniel Eischen wrote: > > > > Is it something recent that broke? Last I knew, libpthread was working > > on amd64 with mozilla & kde. > > KDE works flawlessly. Mozilla almost works, but suffers from the "mysterious > vanishing" I mentioned. > > If you want to reproduce the problems, either: > (a) Fire up gnome-terminal, open a few new tabs, close them again, repeat > until it crashes. It often takes only 2-3 invocations of "Open Tab" > to make it happen. > (b) Load a handful of MP3 files into XMMS, click the next/previous > track buttons once every few seconds until it crashes. > > Everything seems to work fine if I build libpthread with SYSTEM_SCOPE_ONLY > (at least it hasn't crashed so far.) My current guess is that there's a > bug in context manipulation or signals. I initially thought we weren't > saving enough FPU context in _amd64_save_context, but adding an fxsave > in there didn't help. If KDE & mozilla work, then context switching would work (unless they are specifically creating system-scope threads, but I don't think that is the case). I just ran a simple test case on sledge that created a few cpu bound threads doing FPU operations and it didn't crash. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10406051236030.14185-100000>