From owner-freebsd-questions Thu Mar 2 10:14:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by hub.freebsd.org (Postfix) with SMTP id 302F237C3F1 for ; Thu, 2 Mar 2000 10:14:21 -0800 (PST) (envelope-from wsanborn@uswest.net) Received: (qmail 19429 invoked by alias); 2 Mar 2000 18:06:12 -0000 Delivered-To: fixup-questions@freebsd.org@fixme Received: (qmail 27922 invoked by uid 0); 2 Mar 2000 17:57:20 -0000 Received: from rdslppp159.sttl.uswest.net (HELO milk) (216.160.110.159) by sttlpop5.sttl.uswest.net with SMTP; 2 Mar 2000 17:57:20 -0000 From: To: "John Reynolds~" Date: Thu, 2 Mar 2000 10:02:36 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: xmms 1.0.1 uses 95% cpu Reply-To: wsanborn@uswest.net Cc: questions@freebsd.org Message-ID: <38BE3C3C.17337.42ADED6@localhost> In-reply-to: <14526.35847.54442.475405@hip186.ch.intel.com> References: <20000223215739.B326@marder-1> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just CVSup'ed and made a new kernel. It did not affect XMMS in any way; It still hogs up the CPU. I'm using an AWE-64. On 2 Mar 2000, at 8:43, John Reynolds~ wrote: > I applied the patch found in PR kern/16709 like it was suggested but it had > absolutely zero affect on xmms (version 0.9.5.1 that shipped with 3.4-R). I > fire the thing up and it still chews 95% of the CPU up not even playing a song > ... > > I don't know when things changed--I didn't used to have this behavior. Then I > tried to "upgrade" to xmms-1.0.1 and was having problems of the same sort > mentioned in the quote above (very "jumpy" scope updates and sucking 100% of > the CPU). I blew that away and reverted back to 0.9.5.1 from my 3.4-R CD but > now the problem persists (I don't recall if I'd done a CVSup and "make world" > + kernel inbetween reverting back to 0.9.5.1 ... I CVSup regularly so it is a > good possibility). > > Anyone have any clues? Does the patch in PR kern/16709 fix others' problem? > > -Jr > > ps: running an "older" PCI128 with a 1370. > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | John Reynolds WCCG, CCE, Higher Levels of Abstraction | > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | > | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message