From: Nicholas Knight <tegeran@home.com>
To: Adrian Cox <adrian@humboldt.co.uk>, tegeran@home.com
Cc: t.sailer@alumni.ethz.ch, Thomas Sailer <sailer@scs.ch>,
jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: via82cxxx_audio locking problems
Date: Thu, 20 Sep 2001 05:24:38 -0700 [thread overview]
Message-ID: <01092005243800.01369@c779218-a> (raw)
In-Reply-To: <3BA9AB43.C26366BF@scs.ch> <01092004333500.00182@c779218-a> <3BA9DBED.9020401@humboldt.co.uk>
In-Reply-To: <3BA9DBED.9020401@humboldt.co.uk>
On Thursday 20 September 2001 05:07 am, Adrian Cox wrote:
> Nicholas Knight wrote:
> > thankyouthankyouthankyouthankyouthankyou
> > Adrian Cox was working on this after I raised the issue on the list,
> > but nobody got anywhere. All we knew was that there were temporary
> > lockups appearing when anything was using the mixer.
>
> This is the right answer. The reason some of us didn't see a problem
> may actually be quite simple: we were using very small buffers in xmms.
> Once I increased the xmms buffer size the problem became visible.
Interesting, I just experimented with it, bringing down the buffers to
200ms (low as they'll go) and pre-buffer % to 0, does seem to have an
effect, but it doesn't "fix" the problem for me... Should I just conclude
that the tolerance for this is higher on some boards/chips than on
others, and that once THIS problem is fixed, it'll go away and I can
happily use my volume control again?
next prev parent reply other threads:[~2001-09-20 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 8:39 via82cxxx_audio locking problems Thomas Sailer
2001-09-20 11:33 ` Nicholas Knight
2001-09-20 12:07 ` Adrian Cox
2001-09-20 12:24 ` Nicholas Knight [this message]
2001-09-20 13:40 ` André Dahlqvist
2001-09-20 13:41 ` Thomas Sailer
2001-09-21 9:27 ` Thomas Sailer
2001-09-21 12:06 ` André Dahlqvist
2001-09-21 13:01 ` Lockups fixed! (Was: via82cxxx_audio locking problems) André Dahlqvist
2001-09-20 16:33 ` via82cxxx_audio locking problems Jeff Garzik
2001-09-21 7:50 ` Adrian Cox
2001-09-21 8:36 ` David Chow
2001-09-21 8:50 ` David Chow
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=01092005243800.01369@c779218-a \
--to=tegeran@home.com \
--cc=adrian@humboldt.co.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sailer@scs.ch \
--cc=t.sailer@alumni.ethz.ch \
/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