From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 5 09:51:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B196716A4CE; Sat, 5 Jun 2004 09:51:33 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7025043D5D; Sat, 5 Jun 2004 09:51:33 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i55GpMtD022725; Sat, 5 Jun 2004 12:51:22 -0400 (EDT) Date: Sat, 5 Jun 2004 12:51:22 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Tim Robbins In-Reply-To: <20040605163123.GA29935@cat.robbins.dropbear.id.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Sean McNeil cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:51:33 -0000 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