alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: George Anchev <studio@anchev.net>
To: alsa-devel@alsa-project.org
Subject: Re: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write
Date: Mon, 27 Aug 2018 17:09:02 +0300	[thread overview]
Message-ID: <20180827170902.18ca83f5@localhost> (raw)
In-Reply-To: <s5hbm9o7zy3.wl-tiwai@suse.de>

On Mon, 27 Aug 2018 14:32:04 +0200 Takashi Iwai wrote:

> It's grumbling PulseAudio about the wakeup timing
> isn't strictly synced with the reported avail size.

Is that not a problem? (considering it appears in red
in the log)

> In most case, you can ignore it unless you actually
> have the audible problem.

I have been doing this since Leap 42.1 (perhaps even
before since 13.2) but I thought it may be time to
report it.

--
George

  reply	other threads:[~2018-08-27 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 22:48 alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write George Anchev
2018-08-27 12:32 ` Takashi Iwai
2018-08-27 14:09   ` George Anchev [this message]
2018-08-27 14:18     ` Takashi Iwai
2018-08-27 14:23       ` George Anchev

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=20180827170902.18ca83f5@localhost \
    --to=studio@anchev.net \
    --cc=alsa-devel@alsa-project.org \
    /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).