All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: Todd Deshane <todd.deshane@xen.org>,
	xen-devel mailing list <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Sound not working properly on Xen Dom0, but works on native
Date: Thu, 9 Feb 2012 19:55:44 +0000	[thread overview]
Message-ID: <4F3424C0.2050103@citrix.com> (raw)
In-Reply-To: <20120209174210.GA14007@andromeda.dapyr.net>

On 09/02/12 17:42, Konrad Rzeszutek Wilk wrote:
> On Sat, Jan 28, 2012 at 01:19:23PM -0500, Todd Deshane wrote:
>> On Tue, Jan 17, 2012 at 11:12 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>>> On Sun, Jan 15, 2012 at 07:12:52PM -0500, Todd Deshane wrote:
>>>> Hi,
>>>>
>>>> I'm doing some testing on Ubuntu 12.04 Alpha. All sounds comes out as
>>>> static on the Dom0 system. (I can PCI passthrough the audio card to a
>>>> DomU and that works). Native sound works fine.
>>>>
>>>> Linux kronos 3.2.0-8-generic-pae #15-Ubuntu SMP Wed Jan 11 15:34:57
>>>> UTC 2012 i686 i686 i386 GNU/Linux
>>>
>>> Did you try 64-bit dom0?
>>
>> 64bit Dom0 works perfectly.
> 
> Aha! I have an inkling this is the
> 7a7546b377bdaa25ac77f33d9433c59f259b9688

This is "x86: xen: size struct xen_spinlock to always fit in
arch_spinlock_t" from the 3.2 stable tree.

There are many spinlock in sound/ affected by the bug fixed by the above
dunno if any would cause sound distortion but there were plenty of
deadlock opportunities though.

David

  reply	other threads:[~2012-02-09 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16  0:12 Sound not working properly on Xen Dom0, but works on native Todd Deshane
2012-01-17 16:12 ` Konrad Rzeszutek Wilk
2012-01-28 18:19   ` Todd Deshane
2012-02-09 17:42     ` Konrad Rzeszutek Wilk
2012-02-09 19:55       ` David Vrabel [this message]
2012-02-10  2:07         ` Todd Deshane
2012-12-19 18:32           ` Konrad Rzeszutek Wilk

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=4F3424C0.2050103@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=todd.deshane@xen.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.