As I mentioned on a thread about flash-plugin a few days ago, I'm having trouble with my sound device getting "stuck" and thereby causing problems for anything that accesses it, like video playback.
Rebooting the machine "fixes" it for a while, but it's unpredictable for how long -- sometimes months go by without it recurring, sometimes it happens every couple of days. Right now I'm in one of the latter phases.
Any suggestions on how I could reset the controller without having to reboot? (Or suggestions for where else I might ask this question?) Below is output from "lshw" for the audio controller, and "lsmod" for the sound modules that are loaded. This is CentOS 4.7.
*-multimedia UNCLAIMED description: Multimedia audio controller product: CK804 AC'97 Audio Controller vendor: nVidia Corporation physical id: d bus info: pci@0000:00:0d.0 version: a2 width: 32 bits clock: 66MHz capabilities: pm bus_master cap_list configuration: latency=0 maxlatency=5 mingnt=2 resources: ioport:d400(size=256) ioport:d000(size=256) memory:ff6fd000-ff6fdfff
snd_intel8x0 36237 3 snd_ac97_codec 65425 1 snd_intel8x0 snd_pcm_oss 52857 0 snd_mixer_oss 22081 2 snd_pcm_oss snd_pcm 92613 3 snd_intel8x0,snd_pcm_oss snd_timer 28357 1 snd_pcm snd_page_alloc 14541 2 snd_intel8x0,snd_pcm gameport 8641 1 snd_intel8x0 snd_mpu401_uart 11457 1 snd_intel8x0 snd_rawmidi 28133 1 snd_mpu401_uart snd_seq_device 12105 1 snd_rawmidi snd 58149 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device soundcore 13345 2 snd
Quoting Bart Schaefer barton.schaefer@gmail.com:
As I mentioned on a thread about flash-plugin a few days ago, I'm having trouble with my sound device getting "stuck" and thereby causing problems for anything that accesses it, like video playback.
Rebooting the machine "fixes" it for a while, but it's unpredictable for how long -- sometimes months go by without it recurring, sometimes it happens every couple of days. Right now I'm in one of the latter phases.
Any suggestions on how I could reset the controller without having to reboot? (Or suggestions for where else I might ask this question?) Below is output from "lshw" for the audio controller, and "lsmod" for the sound modules that are loaded. This is CentOS 4.7.
<snip>
I have similar problems in CentOS 5. I disable and enable the flash plugin in firefox, and it seems to be corrected. My problem may be slightly different, but this is how I 'fix' the problem.
From: Barry Brimer lists@brimer.org
I have similar problems in CentOS 5. I disable and enable the flash plugin in firefox, and it seems to be corrected. My problem may be slightly different, but this is how I 'fix' the problem.
Same here, flash locks out the audio... mplayer gives me: Can't open audio device /dev/dsp: Device or resource busy Closing my browser fixes it... Maybe I should try with ALSA or ESD instead of autodetect which seems to choose OSS...?
JD
On Mon, 2009-04-27 at 08:05 -0700, Bart Schaefer wrote:
As I mentioned on a thread about flash-plugin a few days ago, I'm having trouble with my sound device getting "stuck" and thereby causing problems for anything that accesses it, like video playback.
Rebooting the machine "fixes" it for a while, but it's unpredictable for how long -- sometimes months go by without it recurring, sometimes it happens every couple of days. Right now I'm in one of the latter phases.
------------- You do not have to reboot the machine every time it happens! Use the System Monitor Gnome Applet to kill what ever is using it.
Further more this really seems like a Bug in the way Applications handle killing processes. Why? I have a Client this happens to often. Exactly the way you describe.
One idea why it affects my clients machine is it is running 4.7 and is dog dead slow. Wait 5 minutes and the processes finally exits. In theory it should exit when the app is closed.
johnStanley
On Mon, Apr 27, 2009 at 8:27 AM, JohnS jses27@gmail.com wrote:
You do not have to reboot the machine every time it happens! Use the System Monitor Gnome Applet to kill what ever is using it.
Unfortunately that doesn't help. Once the machine is in this state, then even after using "lsof" to track down all processes that are using the sound device, and killing all of them, the *next* thing to access the sound will play for a few seconds and then lock up.
I once got it to clear up by unloading and reloading all the sound-related kernel modules, but that doesn't repeatably work either.
On Mon, 2009-04-27 at 08:45 -0700, Bart Schaefer wrote:
On Mon, Apr 27, 2009 at 8:27 AM, JohnS jses27@gmail.com wrote:
You do not have to reboot the machine every time it happens! Use the System Monitor Gnome Applet to kill what ever is using it.
Unfortunately that doesn't help. Once the machine is in this state, then even after using "lsof" to track down all processes that are using the sound device, and killing all of them, the *next* thing to access the sound will play for a few seconds and then lock up.
I once got it to clear up by unloading and reloading all the sound-related kernel modules, but that doesn't repeatably work either.
--- Ok then just a question to solve my thinking. What type of machine is this as in Brand. The one I'm see the problem on is a HP 400Mhz Celeron 254MB of ram. My thinking for my clients problem is it is a real slow machine and the processes are taking a long time to exit. But you have to reboot the whole machine. What is the mixer your using? You may can try looking at the Sound Preferences Devices Tab to change the options there to see if that will help.
JohnStanley
On Mon, Apr 27, 2009 at 9:55 AM, JohnS jses27@gmail.com wrote:
Ok then just a question to solve my thinking. What type of machine is this as in Brand.
It's a custom-built desktop tower from Monarch Computer Systems, who seems to have gone out of business almost exactly two years ago. I'd forgotten how long I've had this box.
The one I'm see the problem on is a HP 400Mhz Celeron 254MB of ram.
P4 @ 3GHz w/ 2GB here.
What is the mixer your using?
/usr/libexec/mixer_applet2 from gnome-applets-2.8.0-9.el4
You may can try looking at the Sound Preferences Devices Tab to change the options there to see if that will help.
I'm on CentOS 4. There is no "Devices" tab on Sound Preferences. System Settings -> Soundcard Detection locks up on the test sound, just like any other app ...
On Mon, 2009-04-27 at 12:43 -0700, Bart Schaefer wrote:
On Mon, Apr 27, 2009 at 9:55 AM, JohnS jses27@gmail.com wrote:
Ok then just a question to solve my thinking. What type of machine is this as in Brand.
It's a custom-built desktop tower from Monarch Computer Systems, who seems to have gone out of business almost exactly two years ago. I'd forgotten how long I've had this box.
The one I'm see the problem on is a HP 400Mhz Celeron 254MB of ram.
P4 @ 3GHz w/ 2GB here.
Well that solves my wonders. Yours is way faster than my clients.
What is the mixer your using?
/usr/libexec/mixer_applet2 from gnome-applets-2.8.0-9.el4
You may can try looking at the Sound Preferences Devices Tab to change the options there to see if that will help.
I'm on CentOS 4. There is no "Devices" tab on Sound Preferences. System Settings -> Soundcard Detection locks up on the test sound, just like any other app ...
Ahh.. Hmm If it helps my client has 4.7 and when he/she run mplayer that's when the same problem starts. It happens with and app that plays audio. Let me look tonight to see what exact mixer/driver my clients is using so I don't tell you a tail.
JohnStanley
-
Barry Brimer -
Bart Schaefer -
John Doe -
JohnS