Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: snd_hda_intel: Woke up but no data
Date: Wed, 17 Aug 2022 23:46:46 +0200 (CEST)	[thread overview]
Message-ID: <20220817214646.29F14F80130@alsa1.perex.cz> (raw)
In-Reply-To: <1660772802439182997-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #262 was opened from shmohawk:

```
Aug 17 01:11:23 hellokitty pulseaudio[12938]: [alsa-sink-CX20590 Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Aug 17 01:11:23 hellokitty pulseaudio[12938]: [alsa-sink-CX20590 Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Aug 17 01:11:23 hellokitty pulseaudio[12938]: [alsa-sink-CX20590 Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
```

It is symptomous with a crackling sound for ~5 seconds after any playback starts.

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/262
Repository URL: https://github.com/alsa-project/alsa-lib

       reply	other threads:[~2022-08-17 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1660772802439182997-webhooks-bot@alsa-project.org>
2022-08-17 21:46 ` GitHub issues - opened [this message]
     [not found] <1660775636983509064-webhooks-bot@alsa-project.org>
2022-08-17 22:34 ` snd_hda_intel: Woke up but no data GitHub issues - edited
     [not found] <1660860791542484045-webhooks-bot@alsa-project.org>
2022-08-18 22:13 ` GitHub issues - reopened

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=20220817214646.29F14F80130@alsa1.perex.cz \
    --to=github@alsa-project.org \
    --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