All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Daniel Griscom <griscom@suitable.com>
Cc: Alsa Developer <alsa-devel@alsa-project.org>
Subject: Re: Missing exactly 3 of 8 audio packets?
Date: Thu, 22 Nov 2012 22:32:23 +0100	[thread overview]
Message-ID: <50AE99E7.6080008@gmail.com> (raw)
In-Reply-To: <p06240816ccd2e5cc9db7@[192.168.1.8]>

On 21.11.2012 21:13, Daniel Griscom wrote:
> On to the next problem we're having with our USB audio card. Recap: 
> simple USB Audio Class embedded stereo audio card, running at 44.1kHz 
> or 48kHz, using the 3.6.6 kernel and its associated ALSA modules to 
> drive it, running on Jetway ND9D-2700, with an Atom D2700 and NM10 
> chipset. Output of "sudo lsusb -v" for card is appended below.
> 
> Problem: we're experiencing strange hiccups in the delivery of audio 
> from the motherboard to the card. At 48kHz, the motherboard should 
> send a 6-frame packet to the card once per high-speed microframe 
> (every 125us). This usually works, but sometimes there are two 
> closely related failures:
> 
> 1) Once in a while (every few seconds or minutes) a single packet 
> will be missed
> 
> 2) Once in a longer while (every few minutes or hours), the system 
> will go into a continuing error condition where three of every eight 
> packets are missed.
> 
> In both cases, "missed" means that ALSA consumes the output audio 
> from my motherboard application, but never sends a packet to the 
> audio card. No USB errors, no logged messages; it just disappears.

I missed that detail before. What makes you so sure ALSA actually
consumes audio it never sends out? Are you sending a test pattern which
is interrupted in your USB analyzer traces?


Daniel

  parent reply	other threads:[~2012-11-22 21:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 20:13 Missing exactly 3 of 8 audio packets? Daniel Griscom
2012-11-22 21:01 ` Daniel Mack
2012-11-22 21:32 ` Daniel Mack [this message]
2012-11-25  3:33   ` Daniel Griscom
2012-11-25 12:43     ` Daniel Mack
2012-11-25 16:39       ` Clemens Ladisch
2012-11-26  3:14         ` Daniel Griscom
2012-11-26 21:32           ` Clemens Ladisch
2012-11-25 22:23       ` Daniel Griscom
2012-11-26  7:19         ` Daniel Mack
2012-11-26 21:23           ` Daniel Griscom
2012-11-27 11:48             ` [alsa-devel] " Daniel Mack
2012-11-27 17:01               ` Daniel Griscom
2012-11-27 17:21                 ` Clemens Ladisch
2012-11-27 18:40                   ` Daniel Griscom
2012-11-27 19:46                     ` Clemens Ladisch
2012-11-27 20:10                       ` Daniel Griscom
     [not found]               ` <50B4A870.7040201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-27 17:20                 ` [alsa-devel] " Alan Stern
     [not found]                   ` <Pine.LNX.4.44L0.1211271213580.1489-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-12-03 21:04                     ` Sarah Sharp
  -- strict thread matches above, loose matches on Subject: below --
2012-11-29 20:35 Daniel Griscom
2013-01-06 17:42 ` Clemens Ladisch

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=50AE99E7.6080008@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=griscom@suitable.com \
    /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.