alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: 2.6.34-rc1: regression: ^Z no longer stops sound
Date: Wed, 24 Mar 2010 12:47:37 -0400	[thread overview]
Message-ID: <4BAA4229.9010506@tmr.com> (raw)
In-Reply-To: <4BA8CB73.80400@ladisch.de>

Clemens Ladisch wrote:
> Pavel Machek wrote:
>   
>> On Sun 2010-03-14 17:20:13, Bill Davidsen wrote:
>>     
>>> Pavel Machek wrote:
>>>       
>>>> 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.
>>>>         
>>> 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?
>>>       
>> It happened reliably so far, yes.
>>     
>
> 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?
>   

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

  reply	other threads:[~2010-03-24 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14  7:58 2.6.34-rc1: regression: ^Z no longer stops sound Pavel Machek
2010-03-14 21:20 ` Bill Davidsen
2010-03-23 13:59   ` Pavel Machek
2010-03-23 14:08     ` Clemens Ladisch
2010-03-24 16:47       ` Bill Davidsen [this message]
2010-03-15  7:27 ` Takashi Iwai
2010-03-15  7:41   ` Pavel Machek
2010-03-15  7:46     ` Jaroslav Kysela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BAA4229.9010506@tmr.com \
    --to=davidsen@tmr.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).