From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
alsa-user@lists.sourceforge.net
Subject: ALSA burps, 2.6.7-rc2 VIA VT8233
Date: Thu, 10 Jun 2004 20:36:12 -0400 [thread overview]
Message-ID: <40C8FE7C.2060404@blue-labs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
This machine spams dmesg _very_ frequently with the following message:
ALSA sound/pci/via82xx.c:737: invalid via82xx_cur_ptr, using last
valid pointer
It doesn't happen constantly but comes in bursts. I haven't any idea
what triggers it since I can be playing 20 minutes without any messages
then there will be 50 of them with no change in computer usage.
David
[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]
begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard
next reply other threads:[~2004-06-11 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 0:36 David Ford [this message]
2004-06-11 10:02 ` ALSA burps, 2.6.7-rc2 VIA VT8233 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=40C8FE7C.2060404@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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