[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Problems with audio device pass-through with the latest xen-unstable


  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
  • Date: Mon, 14 Dec 2009 17:52:45 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 14 Dec 2009 07:53:03 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=oNa8e6iEOIedJBn5V45KSqCwMCux92VWi8x54+ETNumWYK5es4/Sz8K3qnWhoOx8RG oAQfRarkiB+6PTD/fZz+s6jqcmFvbL/x4AKTZEo9XL4k3Nxy6ihuVxuJJib9/MjWb3ZU VTDSmFK3Y4JczZT95hlxwG6Oio+OwUBCaUWww=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Below is the 'lspci' of the audio device which doesn't work. You can
see that the BAR is aligned, and also, i'm pretty sure that the 'xm'
won't allow assigning PT device with un-aligned BAR.

00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
        Subsystem: Lenovo Device 20f2
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx+
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin B routed to IRQ 21
        Region 0: Memory at f2920000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<64ns, L1 <1us
                        ExtTag- RBE- FLReset+
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq-
AuxPwr+ TransPend-
                LnkCap: Port #0, Speed unknown, Width x0, ASPM
unknown, Latency L0 <64ns, L1 <1us
                        ClockPM- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed unknown, Width x0, TrErr- Train-
SlotClk- DLActive- BWMgmt- ABWMgmt-
        Kernel driver in use: pciback
        Kernel modules: snd-hda-intel


On Mon, Dec 14, 2009 at 5:28 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Mon, Dec 14, 2009 at 05:30:16PM +0200, Tom Rotenberg wrote:
>> Hi,
>>
>> I'm using the latest xen-unstable (changeset:20605:8f304c003af4), and
>> i found out, that for some reason, there is a problem with audio
>> pass-through on my Lenovo machines (i have tested it on both Lenovo
>> X200 & Lenovo T400/T500). The problem is, that fater i pass-through
>> the audio device (00:1b.0 Audio device: Intel Corporation 82801I (ICH9
>> Family) HD Audio Controller (rev 03)), to the domU Windows XP, it
>> doesn't identify any audio/media device. i have made sure, i have the
>> Microsft UAA high-definition audio bus driver, and i still don't see
>> any audio device.
>>
>> It looks like a specific problem, because on a Dell e6400 machine the
>> audio pass-through works fine.
>>
>> Does anyone knows about such issue? or can guide me to where the
>> problem might be?
>
> Could you send me the lspci -vvv output of both devices? That is the one
> working and non-working.
>
> Also is there anything in the QEMU log?
>
> One of the items that has not yet been back-ported from 2.6.18 is
> making the BARs page-aligned... and I wonder if that is what you
> are hitting (thought the more I think about it the less I think it is that
> - the xm code will give you a fat warning about this).
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.