After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 127814 - Rhythmbox freezes my computer
Rhythmbox freezes my computer
Status: RESOLVED NOTGNOME
Product: rhythmbox
Classification: Other
Component: general
0.5.1
Other Linux
: Normal major
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-24 15:42 UTC by Julien Olivier
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Julien Olivier 2003-11-24 15:42:26 UTC
If I let my computer play music without touch any key or moving the mouse,
after a while the CPU starts being used at 100%. If I then try to mouse the
mouse it works, but I can't click, and I can't switch to the terminal using
CTRL-ALT-1. It seems that the system is frozen.

I can reproduce the bug using RB 0.6.0 and RB 0.6.1 using gstreamer or xine
backends, and using ESD or not.

Someone told me that he had the same problem on Fedora too, and that
switching to KDE/Juk fixed the problem. So I guess this problem is related
to RB, or to something else in GNOME.

This bug happens even if I run only rhythmbox (no other app) within the
GNOME desktop.

My sound card is the following (from lspci): 00:1f.5 Multimedia audio
controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 05)

I didn't have this problem when using Redhat 9 with rhythmbox 0.5.2 and
prior versions on the same computer.
Comment 1 Julien Olivier 2003-11-24 16:13:06 UTC
Looking at my latest /var/log/messages, I found the following lines
just before the computer's forced restart. Can it have a relation ?



Nov 24 13:05:11 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:05:37 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:05:37 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:05:57 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:05:57 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:06:10 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:06:10 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:06:32 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:06:32 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:06:41 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:06:41 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:06:56 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:06:56 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:07:30 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:07:30 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:07:45 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:07:45 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:07:59 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:07:59 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:08:10 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:08:10 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:08:19 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:08:19 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:08:57 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:08:57 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:09:13 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:09:13 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:09:45 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:09:45 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:09:49 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:09:49 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:09:58 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:09:58 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:10:43 localhost kernel: i810_audio: drain_dac, dma timeout?
Nov 24 13:11:04 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:11:04 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:11:32 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:11:32 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:12:26 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:12:26 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:12:46 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:12:46 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:13:32 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:13:32 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:15:14 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:15:15 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:15:31 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:15:31 localhost modprobe: modprobe: Can't locate module
sound-service-1-3
Nov 24 13:20:48 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:20:48 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:20:48 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:20:48 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:36:03 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:36:03 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:36:03 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:36:03 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:51:32 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:51:32 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:51:32 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 13:51:32 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 13:55:05 localhost kernel: i810_audio: drain_dac, dma timeout?
Nov 24 13:59:08 localhost kernel: i810_audio: drain_dac, dma timeout?
Nov 24 14:06:51 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:06:51 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:06:51 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:06:51 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:22:12 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:22:12 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:22:12 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:22:12 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:37:36 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:37:36 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:37:36 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:37:36 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:40:56 localhost kernel: i810_audio: drain_dac, dma timeout?
Nov 24 14:53:07 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:53:07 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 14:53:07 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 14:53:07 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 15:08:50 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 15:08:50 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Nov 24 15:08:50 localhost modprobe: modprobe: Can't locate module
sound-slot-1
Nov 24 15:08:50 localhost modprobe: modprobe: Can't locate module
sound-service-1-0
Comment 2 Julien Olivier 2003-11-25 13:47:42 UTC
Today, I could reproduce the bug using XMMS on GNOME. I guess it's not
a bug in Rhythmbox then.

Sorry for the noise, closing.
Comment 3 Julien Olivier 2003-11-26 12:40:51 UTC
It seems that the bug can't be reproduced if not using GNOME (I tried
with TWM, and no GNOME-related tool).

Now, I have no idea which GNOME compsant causes the freeze. So I'll
re-open the bug but I'll need help to determine the source of the
problem. Is there any GNOME module know to be able to cause
sound-related freezes ? (I don't use ESD, and the bug can be
reproduced after a rpm -e esound --nodeps, so it's not ESD)
Comment 4 Bastien Nocera 2003-11-26 12:57:16 UTC
If your computer freezes, it's a kernel problem, not a GNOME/Rhythmbox
or whatever else problem.

Furthermore, I'd advise you to stop using Beta kernels, it's a bad idea.
Comment 5 Julien Olivier 2003-11-26 13:14:43 UTC
 1) Any piece of software entering a endless loop can freeze the
system. Not only the kernel. By the way, if it was a kernel freeze, I
couldn't move my mouse, could I.

 2) I'm not using a Beta kernel. I'm using the one coming with Fedora
Core 1.

 3) If it wasn't GNOME related, it would when not using GNOME. And it
doesn't.
Comment 6 Bastien Nocera 2003-11-26 13:18:34 UTC
So it's not your computer freezing. Please get a backtrace of the
application locking:
http://bugzilla.gnome.org/getting-traces.cgi
Comment 7 Julien Olivier 2003-11-26 13:26:40 UTC
Yes, sorry. the computer is not really frozen but I can't hear sound
anymore, I can't click anywhere and I can't switch to a virtual
terminal using CTRL-ALT-x. But I can move the mouse...

As for the backtrace, I would be glad to do it, but how do I
determinate which app locks my system ? Using "top" ?
Comment 8 Bastien Nocera 2003-11-26 13:31:40 UTC
ssh into the machine, and top/gdb etc. are your new friends.
Comment 9 Julien Olivier 2003-11-26 13:34:43 UTC
Well, I guess it's hopeless then, as I have only one computer :(
Comment 10 Julien Olivier 2003-11-27 15:16:50 UTC
I have done 2 tests:

1) I let top running in a visible window. When the "freeze" started, I
saw nothing special in top. I don't know, however, whether top was
frozen too or not.

2) I switched from OSS to ALSA. The problem still occurs, but the
error messages I pasted upper don't appear anymore (this was expected
since there were OSS-related errors). That tends to exclude the kernel
from the possible causes, doesn't it ?

I'll now try to reproduce the bug using less and less components of
the GNOME desktop, to see which one is the cause.
Comment 11 Julien Olivier 2003-11-27 17:13:01 UTC
According to this: http://fedora.artoo.net/faq/#AlanCox, appending
apm=off or nohlt might fix the problem.

I'm gone close the bug, try it and re-open the bug if it isn't fixed.

Thanks for your help.
Comment 12 Julien Olivier 2003-11-28 15:15:31 UTC
Appending acpi=on and apm=off to my grub.conf fixed the problem. I
guess it was an apm bug then...
Comment 13 Julien Olivier 2003-11-28 21:08:33 UTC
Aaargh.. bad news:

The freeze happened again, one with acpi=on and apm=off (while idle)
and once with acpi=off, apm=off and nohlt (not even idle)...

What's strange is that, this time, it even happened when not idle. The
only common point to all those freezes is that they happen when
playing music. But as I'm listening to music all day long, it could as
well be a coincidence...

What's also strange is that I let my computer running all night long,
with music running (rhythmbox) on GNOME and all was OK on the morning.

I'm really lost...

I'm setting severity to major as it could make a server totally unusable.
Comment 14 Bastien Nocera 2003-11-28 21:12:53 UTC
Julien, this has obviously nothing to do with Rhythmbox. Could you
please close this bug, and take it somewhere else?
Comment 15 Julien Olivier 2003-11-28 21:27:24 UTC
OK, I'm closing it. I'll ask on Fedora's mailing list because I can't
re-open a bug without knowing which component is broken...