From: Leigh Dyer <leigh@eclinic.com.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] OSS audio debugging
Date: Thu, 10 Jun 2004 17:17:53 +1000 [thread overview]
Message-ID: <1086851873.16982.8.camel@shawn.local> (raw)
Hi all,
I've been playing with the sb16 emulation using a Win2k guest. The Add
New Hardware wizard's hardware probe picked it up and installed it
without any problems, but playing audio quite often resulted in a very
abrupt end to the emulation.
I've tracked the problem down to the AUD_run() function in oss.c. When
writing to the card, it calls SNDCTL_DSP_GETOSPACE, which is apparently
meant to return the amount of data that can be written to the card
without blocking. However, for some reason, occasionally the value
returned in abinfo.bytes is negative. This negative value makes it
through to the write() call, which then fails with an unknown error,
hitting the:
ERRFail ("write audio");
line.
I really don't know much about OSS, so I'm not sure how this should be
handled. Does anyone else know what this could mean? For reference, the
card is an ess1371, running ALSA drivers in OSS emulation mode.
Thanks
Leigh
next reply other threads:[~2004-06-10 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 7:17 Leigh Dyer [this message]
2004-06-10 16:06 ` [Qemu-devel] OSS audio debugging malc
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=1086851873.16982.8.camel@shawn.local \
--to=leigh@eclinic.com.au \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).