linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: nick <xerofoify@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Possible Bug Found with Xonar Stx Driver
Date: Fri, 10 Jul 2015 14:13:38 +0200	[thread overview]
Message-ID: <559FB6F2.2000606@ladisch.de> (raw)
In-Reply-To: <559EFC14.2090408@gmail.com>

nick wrote:
> After running the latest version of Linus's tree I am noticed way more buffering

What exactly do you mean with the word "buffering"?

> when playing music with my Xonar STX card when building kernels then
> under the Ubuntu kernel version of 3.19.16.

Sounds like a change in the disk access patterns.

The audio buffer size is chosen by the playing application (whatever it
is).

> I have tried bisecting it between the releases of 3.18 and 4.0
> and was unable to narrow it down to a buggy commit.

There was no relevant change in the sound driver.


Regards,
Clemens

           reply	other threads:[~2015-07-10 12:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <559EFC14.2090408@gmail.com>]

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=559FB6F2.2000606@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=xerofoify@gmail.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;
as well as URLs for NNTP newsgroup(s).