Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	1136110@bugs.launchpad.net,
	Alan Stern <stern@rowland.harvard.edu>,
	Joseph Salisbury <joseph.salisbury@canonical.com>,
	Tyson Tan <tysontan@mail.com>,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: Asynchronous audio USB chips: choppy playback since 3.8-rc7
Date: Fri, 19 Apr 2013 20:54:25 +0200	[thread overview]
Message-ID: <517192E1.1090609@gmail.com> (raw)
In-Reply-To: <s5hhajnlxlh.wl%tiwai@suse.de>

On 03.04.2013 12:25, Takashi Iwai wrote:
> At Wed, 03 Apr 2013 12:15:25 +0200,
> David Henningsson wrote:
>>
>> Hi ALSA developers,
>>
>> Just to get your attention here on what seems to be an USB audio 
>> regression.
>>
>> The bug is described in detail here:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110?comments=all
>>
>> Quoting the bug:
>>
>> "
>> This bug seems to affect only a certain kind of hardware, which is 
>> called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such 
>> a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so 
>> called "Synchronous USB DAC", uses the clock hosted by the mother board, 
>> which is not affected by this bug.
>>
>> When this bug affects an asynchronous USB DAC, the audio played by the 
>> DAC is constantly interrupted. The playback itself does not stop, but 
>> the output becomes discontinous, filling with constant crackling noises, 
>> destroying everything the DAC plays.
>> "
>>
>> According to the bug reporter, which seems to have done quite a bit of 
>> research, this started between 3.8-rc6 and 3.8-rc7 as well as stable 
>> kernels and the bug also lists a few commits which could be the cause, 
>> none under sound/usb though.
> 
> Yes, there is no commits regarding usb-audio itself between 3.8-rc6
> and rc7, so the likely culprit is in drivers/usb (usually either
> drivers/usb/host or drivers/usb/core).  There are a bunch of changes
> there, so further bisection would be appreciated.

Ok, Joseph Salisbury has build some bisection kernels, and Tyson Tan
relentlessly tested all of them, and it turns out that

3e619d0415 ("USB: EHCI: fix bug in scheduling periodic split transfers")

Is the first bad commit. Also, reverting this commit from the current
mainline head makes the problem disappear.

Alan, any idea?

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110


Thanks,
Daniel

  reply	other threads:[~2013-04-19 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 10:15 Asynchronous audio USB chips: choppy playback since 3.8-rc7 David Henningsson
2013-04-03 10:23 ` Daniel Mack
2013-04-03 13:55   ` Michael Trimarchi
2013-04-03 14:11     ` Michael Trimarchi
2013-04-03 15:00       ` Daniel Mack
2013-04-03 15:19         ` Michael Trimarchi
     [not found]           ` <515C4879.8090208-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2013-04-03 15:37             ` [alsa-devel] " Daniel Mack
2013-04-03 10:25 ` Takashi Iwai
2013-04-19 18:54   ` Daniel Mack [this message]
2013-04-19 20:48     ` Alan Stern
2013-04-19 20:48     ` [alsa-devel] " Alan Stern
2013-04-24 18:30       ` David Henningsson
2013-04-24 19:11         ` Alan Stern

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=517192E1.1090609@gmail.com \
    --to=zonque@gmail.com \
    --cc=1136110@bugs.launchpad.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tiwai@suse.de \
    --cc=tysontan@mail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox