On Tue, 2003-07-22 at 03:52, Bill Rhodes wrote:
On Tue, 21 Jul 2003, Warren Togami wrote:
On Mon, 2003-07-21 at 20:39, Bill Rhodes wrote:
I don't think this has anything to do with XMMS. I can get the CPU to peg at 100% just by dragging windows around, or running ls against /usr/lib (or some other directory with a large number of files). It happens whether XMMS is playing (either MP3 or OGG files) or not. Although anytime the CPU usage gets that high, XMMS skips (for me at least).
What video card? Using stock or 3rd party drivers?
ATI Rage Mobility P/M AGP 2x (Mach64), using stock driver as detected by the installer (ati).
What sound card? Using which driver?
Well, if I can get the CPU to peg without even starting XMMS, why would that matter? But just for the sake of completeness, I've got a Crystal SoundFusion CS 4614 sound card, using the cs46xx driver (whith "thinkpad=1" passed as an option in /etc/modules.conf).
Incidentally, if I boot into runlevel 3 and then ssh in and run 'ls -lR /' remotely, the CPU is fine. If I start X (KDE, in my case) and run that same command from a konsole window, the CPU usage spikes to 100% (looks like X is about 60% and kdeinit is 30%, with the rest being ls). If I run GNOME and ran that same command locally, gnome-terminal likes to grab about 85% of the cpu. Running ls remotely while GNOME is up uses no appreciable CPU.
XMMS skips when I run that command locally, playing either OGG or MP3 files. It does not skip when I run it remotely. I don't think the problem is with XMMS. Any other app (gkrellm, mozilla, gnome-system-monitor, etc) all "skip" (eg, fail to redraw screen bits) when the CPU usage approaches 100%.
I'll go file a bug report with bugzilla.
What's the bug number?
Cheers, Brent
-B
-- Rhl-beta-list mailing list Rhl-beta-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-beta-list