From: Mark McLoughlin <markmc@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Justin M. Forbes" <jforbes@redhat.com>,
Gene Czarcinski <gene@czarc.net>
Subject: Re: [Qemu-devel] Re: audio segfault in qemu-kvm-0.11.0
Date: Fri, 23 Oct 2009 14:50:31 +0100 [thread overview]
Message-ID: <1256305831.31881.78.camel@blaa> (raw)
In-Reply-To: <Pine.LNX.4.64.0910231739270.2740@linmac.oyster.ru>
On Fri, 2009-10-23 at 17:41 +0400, malc wrote:
> On Fri, 23 Oct 2009, malc wrote:
>
> > On Fri, 23 Oct 2009, Mark McLoughlin wrote:
> >
> > > Hi,
> > >
> > > Any ideas on this segfault a Fedora 12 user (Gene, cc-ed) is seeing?
>
> [..snip..]
>
> >
> > Summary: No idea.
> >
>
> FWIW, there's no information whatosever about what audio hardware was
> built and enabled, what sound system was used on the host/guest the
> report is devoid of any useful information (given the state of the
> backtrace)
That's fine, we'd only be delighted to provide some more info.
Our tree is at http://repo.or.cz/w/qemu-kvm/fedora.git
It's based off the stable-0.11 branch
Code is:
if (played) {
hw->ts_helper += played;
audio_capture_mix_and_clear (hw, prev_rpos, played);
}
If it would help you, I could ask Gene to reproduce with a -O0 build
Built with --audio-drv-list=pa,sdl,alsa,oss
Command line was:
QEMU_AUDIO_DRV=none qemu-kvm ... -soundhw es1370
Not a lot of info on exactly what the guest is doing with sound, only
that they are Fedora 11 or Fedora 12 guests
Thanks,
Mark.
next prev parent reply other threads:[~2009-10-23 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 13:16 [Qemu-devel] audio segfault in qemu-kvm-0.11.0 Mark McLoughlin
2009-10-23 13:31 ` [Qemu-devel] " malc
2009-10-23 13:41 ` malc
2009-10-23 13:50 ` Mark McLoughlin [this message]
2009-10-23 14:29 ` malc
2009-10-23 15:11 ` Gene Czarcinski
2009-10-23 17:34 ` 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=1256305831.31881.78.camel@blaa \
--to=markmc@redhat.com \
--cc=av1474@comtv.ru \
--cc=gene@czarc.net \
--cc=jforbes@redhat.com \
--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).