All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bogdan Veringioiu <bogdan.veringioiu@amano.eu>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problems with usb soundcard in kernels > 3.3
Date: Wed, 12 Nov 2014 12:22:17 +0100	[thread overview]
Message-ID: <546342E9.1010101@amano.eu> (raw)
In-Reply-To: <546217FD.1030806@amano.eu>

Hi,

any idea on how to further debug this issue?
Thanks,
Bogdan

On 11/11/2014 03:06 PM, Bogdan Veringioiu wrote:
> Hi,
>
> thanks for your availability.
> There is one message that appears in syslog, but it is always displayed
> when I test with aplay, unregarding the kernel version. It shows both
> with the working kernel (3.2) and with the problematic one (3.16).
>
> --> with kernel 3.2.0-4-686-pae
> /var/log/syslog
> ...
> kernel: [ 2829.369380] 2:1:1: cannot get freq at ep 0x2
> ...
>
> --> with kernel 3.16-0.bpo.2-686-pae
> /var/log/syslog
> ...
> kernel: [  199.353227] usb 2-1: 1:1: cannot get freq at ep 0x2
> ...
>
> Bogdan
>
> On 11/11/2014 02:32 PM, Clemens Ladisch wrote:
>> Bogdan Veringioiu wrote:
>> > The issue I am experiencing is a ~4 seconds delay in playing sound.
>> > I am reproducing the problem using aplay. The sound play is being
>> > delayed by more or less 4 seconds from the moment the file is sent
>> > to the card. I have tested with kernels 3.2 and 3.3, which work
>> > properly. I have noticed this delay/wait when using kernels 3.15,
>> > 3.16.
>>
>> Any messages in the system log when this happens?
>>
>>
>> Regards,
>> Clemens
>>
>

  reply	other threads:[~2014-11-12 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 11:14 Problems with usb soundcard in kernels > 3.3 Bogdan Veringioiu
2014-11-11 13:32 ` Clemens Ladisch
2014-11-11 14:06   ` Bogdan Veringioiu
2014-11-12 11:22     ` Bogdan Veringioiu [this message]
2014-11-12 14:36     ` Clemens Ladisch
2014-11-13 14:29       ` Bogdan Veringioiu

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=546342E9.1010101@amano.eu \
    --to=bogdan.veringioiu@amano.eu \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.