From: Steven Walter <srwalter@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG] random squeaks with cmpci & 2.4.0
Date: Fri, 5 Jan 2001 18:03:50 -0600 [thread overview]
Message-ID: <20010105180349.A6180@hapablap.dyn.dhs.org> (raw)
While playing mp3's on XMMS, I get squeaks at random intervals. It
seems to correlate slightly with disk usage, but other than that it
seems random. These squeaks did not occur with 2.4.0-prerelease, and no
changes to the cmpci driver have occurred between -prerelease and
-final. Was there an interface/semantics change somewhere? The only
change I see directly related to sound is in sound_timer.c, and it was
only to add a semicolon to an empty label. Perhaps related to the VM
changes somehow? The system is an AMD-K6/2 with 64MB ram, and running X
4.0.2 is that makes any difference.
Another interesting sidenote is that the squeaks appear as a spike in
XMMS' "Visual Analyzer" (usually a series of bars to the left of the
track information). Could it be that this is a /userspace/ issue?
--
-Steven
"Voters decide nothing. Vote counters decide everything."
-Joseph Stalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-06 0:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010105180349.A6180@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--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