Hi!

In 2.6.33, hitting ^Z stopped mpg123 in a way you'd expect (both on
thinkpad and geode notebook).

On 2.6.34-rc1, hit ^Z and sound starts looping.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--

[ message continues ]

That's not new, I have seen it back as far as 2.6.27.25 doing a suspend in a VM 
(KVM, no libvirt). But it only happens a few times a year, so I never chased it. 
I hate to report an occasional problem in an obsolete kernel, and I can't 
reproduce it.

Does it happen repeatably with the new kernel?

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--

[ message continues ]

It happened reliably so far, yes.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--

[ message continues ]

This sounds as if the device has been configured to ignore underruns.
What are the contents of /proc/asound/card0/pcm0p/sub0/{sw_params,status}
when it's looping, and when it's really suspended?


Regards,
Clemens
--

[ message continues ]

If you can give me a hint how to read /proc when the machine is 
suspended, other than waking it up, I'll certainly check the next time I 
see it.

But after reading your thought on underruns, I think you right. I see 
from a note  I wrote myself that I get this while pushing a wav file 
over the network to run "play" (from sox) on another machine. Every once 
in a while it finds a musical phrase it really likes. I had assumed it 
was a bug in sox, but a bug or mis-configure in the device fits all of 
the observed cases I've seen.

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein

--

[ message continues ]

At Sun, 14 Mar 2010 08:58:31 +0100,

Is it an OSS app using the kernel OSS emulation or another backend?

The possible cause is the rewrite of PCM hwptr updater.
Jaroslav, could you take a look?


thanks,

Takashi
--

[ message continues ]

Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--

[ message continues ]

I cannot reproduce this problem here. Could you post the contents
of /proc/asound/card0/pcm0p/sub0/status file when you stop the 
audio process and looping starts?

 				Thanks,
 					Jaroslav

-----
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.

--

[ message continues ]

I created a Bugzilla entry at  
https://bugzilla.kernel.org/show_bug.cgi?id=15590
for your bug report, please add your address to the CC list in there, thanks!
-- 
Maciej Rutecki
http://www.maciek.unixy.pl
--

[ message continues ]

It was fixed by patch in 
"[for 2.6.34][PATCH] ALSA: pcm_lib - fix xrun functionality"
thread. It should already be in sound tree.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--

[ message continues ]