From: Nicholas Knight <tegeran@home.com>
To: Paul Jakma <paulj@alphyra.ie>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: via82cxxx_audio driver bug?
Date: Mon, 13 Aug 2001 21:12:44 -0700 [thread overview]
Message-ID: <01081321124401.00204@c779218-a> (raw)
In-Reply-To: <Pine.LNX.4.33.0108131833300.21710-100000@dunlop.itg.ie>
In-Reply-To: <Pine.LNX.4.33.0108131833300.21710-100000@dunlop.itg.ie>
On Monday 13 August 2001 10:46 am, Paul Jakma wrote:
> On Mon, 13 Aug 2001, Nicholas Knight wrote:
> > and if they've seen XMMS or other audio applications with access to
> > /dev/mixer have strange, temporarily lockups when not in
> > root/realtime priority. I've yet to be able to test this with other
> > audio applications besides XMMS.
>
> yes.. i see this too with the via82cxxx_audio driver on my Tyan
> AMD751+Via southbridge board.
>
> /anything/ that accesses /dev/mixer or /dev/dsp while sound is being
/dev/mixer is the sole problem on my end, as long as I block XMMS's
access to /dev/mixer (wether via permissions or pointing it to a device
that doesn't exist), it plays out /dev/dsp alone just fine, except for
the lack of XMMS-side volume control.
> played is locked. Eg, play an mp3 with xmms. while playing, xmms and
> things like the gnome and WM mixer applets are all unresponsive. they
> respond to UI interaction maybe only every 30 seconds or longer.
The UI in other apps is a little iffy on my end, sometimes they lock,
sometimes not.
>
> xmms with real-time priority does not suffer from this
> unresponsiveness.
>
same here
> from the haze of my memory i think this behaviour started with the
> mmap support that Jeff brought in 1.1.13 or 1.1.14. but i can't be
> sure.
what version was in kernel 2.4.3? I first started reporting this when I
installed Mandrake 8.0 and noticed it a couple months ago.
>
> I've tried playing with the size of the buffers
> (VIA_MAX_BUFFER_DMA_PAGES) and the _TIME and FRAG_ defines. best
> result was that perioid of the unresponsiveness was reduced slightly,
> but not eliminated (by reducing the buffering times and number of
> fragments).
>
> > Thanks.
>
> regards,
>
> --paulj
next prev parent reply other threads:[~2001-08-14 4:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 14:19 via82cxxx_audio driver bug? Nicholas Knight
2001-08-13 15:19 ` Adrian Cox
2001-08-14 4:09 ` Nicholas Knight
2001-08-14 6:47 ` Martin Hoeller
2001-08-14 8:25 ` Adrian Cox
2001-08-13 17:36 ` Anton Altaparmakov
2001-08-13 17:46 ` Paul Jakma
2001-08-14 4:12 ` Nicholas Knight [this message]
2001-08-14 11:06 ` Paul Jakma
2001-08-14 11:28 ` Nicholas Knight
2001-08-14 19:01 ` Petr Baudis
[not found] <fa.csmnkev.1i5mrbt@ifi.uio.no>
[not found] ` <fa.fu9gjtv.lli1j7@ifi.uio.no>
[not found] ` <3B793D00.4090501@nyc.rr.com>
2001-08-14 15:05 ` Adrian Cox
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=01081321124401.00204@c779218-a \
--to=tegeran@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulj@alphyra.ie \
/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