From: Guido Aulisi <guido.aulisi@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: Regression in kernel 3.19-rc5 for usb2 scarlett 18i20
Date: Mon, 26 Jan 2015 14:28:14 +0100 [thread overview]
Message-ID: <CAEw7SVG58Pbc==U5abDTYvUA0ukHnpSU4eQ5FNL77fr6Q47gGQ@mail.gmail.com> (raw)
In-Reply-To: <s5hh9vd1ymg.wl-tiwai@suse.de>
I will ASAP, now I'm not at home.
IMHO I think this is something about usb than the mixer,
because I didn't use it, I only noticed the xruns even without playing audio.
I didn't try 3.18, because it isn't shipped with fedora yet.
Ciao
2015-01-26 14:04 GMT+01:00 Takashi Iwai <tiwai@suse.de>:
> At Sun, 25 Jan 2015 12:42:22 +0100,
> Guido Aulisi wrote:
>>
>> Hi,
>> I noticed a regression in 3.19-rc5 kernel (as shipped by fedora rawhide)
>> with usb2 focusrite scarlett 18i20.
>> I get a lot of xruns with jack, even at 1024 frame buffer and 2 periods.
>> In 3.17.8 it works quite well without xruns at the same settings.
>>
>> I use a fedora 20 (64bit) laptop with 8GB ram, I only installed the
>> rawhide kernel to try the new included scarlett mixer, no other software
>> components changed.
>>
>> I can try to do some other test, but compiling the kernel on this laptop
>> is time consuming.
>>
>> Thanks
>> Guido
>
> Looks like a regression in the recent rework for Scarlett devices.
> Chris, do you have any clue?
>
> In anyway, Guido, could you give lsusb -v output (for the relevant
> part)?
>
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2015-01-26 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 11:42 Regression in kernel 3.19-rc5 for usb2 scarlett 18i20 Guido Aulisi
2015-01-26 13:04 ` Takashi Iwai
2015-01-26 13:28 ` Guido Aulisi [this message]
2015-01-26 13:31 ` Takashi Iwai
2015-01-26 14:30 ` Chris J Arges
2015-01-26 22:32 ` Guido Aulisi
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='CAEw7SVG58Pbc==U5abDTYvUA0ukHnpSU4eQ5FNL77fr6Q47gGQ@mail.gmail.com' \
--to=guido.aulisi@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=chris.j.arges@canonical.com \
--cc=tiwai@suse.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.