Comment 170 for bug 178442

@pablomme, why I want you to test this on Natty is for two reasons:
1) It's easier for me (less administration) to fix something in the upcoming release (Natty) than in stable releases (Lucid, Maverick). In fact, we're about to run out of time for Natty as it starts go into its testing phase with various degrees of freezes... :-/
2) The SRU policy - which controls how things can be updated in stable releases - dictates that the fix should first be verified in the unstable release before considering backporting the fix to a stable release.
Therefore testing on Maverick is not good enough at this point, sorry.

@Mike, thanks for testing. You seem to be suffering from underruns on the client side, which might or might not be related to this issue, let's try to figure out.
Could you please try the following and see and if it helps:
 - Start pulseaudio in the logging mode
 - Make sure no other CPU intensive or audio applications are running at the same time. In particular, make sure gnome-volume-control is not open - and wait 10 seconds after having closed gnome-volume-control before starting the sound test.
 - Go into alsamixer and make sure volume is at 75 - 100%, are there controls labeled "DAC 0" and "DAC 1"? If so make sure they are also turned on.
 - Use this terminal command to test sound: "speaker-test -D pulse -t sine -c 2"
 - Afterwards, please attach the resulting pulseaudio log and in addition, an alsa-info according to https://wiki.ubuntu.com/Audio/AlsaInfo
Thanks!