Date: Thu, 2 Mar 2000 08:43:03 -0700 (MST) From: John Reynolds~ <jreynold@sedona.ch.intel.com> To: Mark Ovens <mark@dogma.freebsd-uk.eu.org> Cc: Roman Shterenzon <roman@xpert.com>, questions@freebsd.org Subject: Re: xmms 1.0.1 uses 95% cpu Message-ID: <14526.35847.54442.475405@hip186.ch.intel.com> In-Reply-To: <20000223215739.B326@marder-1> References: <88483183@toto.iv> <14516.160.72062.803076@hip186.ch.intel.com> <20000223215739.B326@marder-1>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Wednesday, February 23, Mark Ovens wrote: ] > > OK, I had the same problem (xmms-0.9.5.1 was OK though) with the > graphic equalizer only being updated ~ once per second. Anyway, the > fix is to apply the patch for /usr/src/sys/pci/es1370.c (even if your > chipset is, like mine, es1371 - es1370.c is still used) in PR > kern/16709 and re-build your kernel. xmms-1.0.1 works fine now, > except... > > Any of you guys have a problem with adjusting the volume with the > cursor keys? If you drag the slider to somewhere near 50% and then use > the arrow-up and arrow-down keys does the volume (and the VOLUME: n% > display) work properly? Mine only increases, it won't decrease. I've > found the cause of the problem and am working out the best solution > but would be interested how many others are thus afflicted. > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14526.35847.54442.475405>