From: Robert Hancock <hancockrwd@gmail.com>
To: Alsa-Devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>,
LydiaWang@viatech.com.cn, Logan Li <loganli@viatech.com.cn>,
Harald Welte <HaraldWelte@viatech.com>
Subject: VIA VT1828S hda_intel errors
Date: Thu, 29 Oct 2009 19:05:15 -0600 [thread overview]
Message-ID: <4AEA3BCB.5040202@gmail.com> (raw)
I've been using the VT1828S codec support from ALSA git for the last few
weeks. It seems to work fine, but there are some problems showing up in
dmesg:
Oct 25 20:46:14 newcastle kernel: ALSA sound/pci/hda/hda_intel.c:683: No
response from codec, disabling MSI: last cmd=0x02af0900
Oct 25 20:46:15 newcastle kernel: ALSA sound/pci/hda/hda_intel.c:698:
azx_get_response timeout, switching to polling mode: last cmd=0x02af0900
It seems like the cmd isn't always the same, previously it was
0x024f0c00. Is there something bad about this command that could be
causing the response timeout? Also, disabling MSI for one occurrence of
this seems a bit paranoid..
Also saw one of these:
Oct 26 21:13:20 newcastle kernel: hda-intel: IRQ timing workaround is
activated for card #0. Suggest a bigger bdl_pos_adj.
and PulseAudio also complained:
Oct 26 00:27:50 newcastle pulseaudio[16530]: alsa-sink.c: ALSA woke us
up to write new data to the device, but there was actually nothing to write!
Oct 26 00:27:50 newcastle pulseaudio[16530]: alsa-sink.c: Most likely
this is a bug in the ALSA driver 'snd_hda_intel'. Please report this
issue to the ALSA developers.
Oct 26 00:27:50 newcastle pulseaudio[16530]: alsa-sink.c: We were woken
up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0
or another value < min_avail.
next reply other threads:[~2009-10-30 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 1:05 Robert Hancock [this message]
2009-10-30 12:31 ` VIA VT1828S hda_intel errors Takashi Iwai
2009-11-01 20:03 ` Robert Hancock
2009-11-02 10:27 ` Takashi Iwai
2009-11-03 4:55 ` Robert Hancock
2009-11-04 23:52 ` Robert Hancock
2009-11-05 6:59 ` Takashi Iwai
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=4AEA3BCB.5040202@gmail.com \
--to=hancockrwd@gmail.com \
--cc=HaraldWelte@viatech.com \
--cc=LydiaWang@viatech.com.cn \
--cc=alsa-devel@alsa-project.org \
--cc=loganli@viatech.com.cn \
--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.