From owner-freebsd-hackers Fri Jul 27 9:56:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 05E9937B403 for ; Fri, 27 Jul 2001 09:56:49 -0700 (PDT) (envelope-from boshea@netapp.com) Received: from frejya.corp.netapp.com (frejya.corp.netapp.com [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f6RGuEX07459; Fri, 27 Jul 2001 09:56:15 -0700 (PDT) Received: from shaolin.hq.netapp.com (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f6RGuDY00212; Fri, 27 Jul 2001 09:56:13 -0700 (PDT) Received: (from boshea@localhost) by shaolin.hq.netapp.com (8.9.3/8.9.3) id JAA41780; Fri, 27 Jul 2001 09:56:10 -0700 (PDT) (envelope-from boshea) Date: Fri, 27 Jul 2001 09:56:10 -0700 From: "Brian O'Shea" To: Bjoern Fischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Thread problem in xmms Message-ID: <20010727095610.O489@ricochet.net> Reply-To: boshea@ricochet.net Mail-Followup-To: Brian O'Shea , Bjoern Fischer , freebsd-hackers@FreeBSD.ORG References: <20010727113951.C337@broccoli.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <20010727113951.C337@broccoli.no-support.loc>; from bfischer@Techfak.Uni-Bielefeld.DE on Fri, Jul 27, 2001 at 11:39:51AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It could also be a problem with xmms. You might start with the maintainer of the xmms port. The maintainer is listed in the top level Makefile for the port. Cheers, -brian On Fri, Jul 27, 2001 at 11:39:51AM +0200, Bjoern Fischer wrote: > Hello, > > is it possible that xmms triggers a problem in FreeBSD's thread > implementation? It happens often that xmms gets stuck in > _thread_sys_poll(): > > (gdb) info threads > 7 process 332, thread 7 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > 6 process 332, thread 6 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > 5 process 332, thread 5 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > 4 process 332, thread 4 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > 3 process 332, thread 3 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > 2 process 332, thread 2 0x28439d44 in _thread_kern_sched () > from /usr/lib/libc_r.so.4 > * 1 process 332, thread 1 0x2843b754 in _thread_sys_poll () > from /usr/lib/libc_r.so.4 > (gdb) > > Is this a known problem? > > Björn Fischer > > -- > -----BEGIN GEEK CODE BLOCK----- > GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ > K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ > ------END GEEK CODE BLOCK------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Brian O'Shea To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message