[pulseaudio-discuss] pulseaudio timing out accepting connections

[Brian J. Murrell]

On Wed, 2008-12-10 at 10:01 -0500, Sean McNamara wrote:
> 
> Are you running PA in realtime mode? Does top say that its priority is "RT"?

Nope.  It says it's "20".

> Yeah, it sounds like PA is stuck in a tight loop trying to access
> ALSA. I've never encountered this before, and I've used Intrepid a
> bit. I'm thinking either you have a custom compiled version of a
> library that PA depends on;

Nope.  Everything here is stock.

> or, you have some strange hardware.

# cat /proc/asound/cards 
 0 [Live           ]: EMU10K1 - SBLive! Value [CT4832]
                      SBLive! Value [CT4832] (rev.7, serial:0x80271102) at 0x9c00, irq 17
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfe024000 irq 22
 2 [U0x46d0x8c5    ]: USB-Audio - USB Device 0x46d:0x8c5
                      USB Device 0x46d:0x8c5 at usb-0000:00:0b.1-2, high speed
 3 [Bt878          ]: Bt87x - Brooktree Bt878
                      Brooktree Bt878 at 0xfdafe000, irq 16

AFAIK, pulse is just using the EMU10K1, which is my main speakers.

Strangely pulse does not detect the other devices.

> Can you tell me what kinds of applications are currently active as
> sinks on your PA?

Just Rhythmbox at the moment.

> What protocol are they connecting through?

Whatever gnome is providing.  I have the sound properties in Gnome set
to use Pulseaudio.

> Any
> ALSA<->Pulse apps?

Not sure.  How could I determine that for you?

> Just as data points. Also, post an lspci

00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
04:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
04:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
04:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
04:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
04:09.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)

> (and also
> an lsusb if you have a USB soundcard).

No USB soundcards.  Oh.  I guess the mic on the webcam counts.

Bus 002 Device 003: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 013: ID 03f0:1411 Hewlett-Packard PSC 750
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

> Nope, there's no guarantee of that.

~sigh~  So in order to get everyone happy again, I have to restart my
entire desktop session?

> Clients have control over the
> terms under which they try to connect to PA.

But if a pulseaudio server goes away (is killed) shouldn't a client see
that and try to reconnect?

> If they're trying to
> communicate and they're timing out,

Wouldn't they get something more positive, along the lines of an
ECONNREFUSED from a pulseaudio server that has been killed?

> if
> they connect and get an error, they may also give up and refuse to
> proceed. With some apps you may have to restart them. Others might
> just keep a full buffer of audio and unload it as soon as they can get
> back into PA.

OK.

b.