This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: AW: Re: PCI passthrough problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: AW: Re: PCI passthrough problem
From: Christian Tramnitz <chris.ace@xxxxxxx>
Date: Mon, 28 Sep 2009 13:30:36 +0200
Delivery-date: Mon, 28 Sep 2009 04:32:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <22297.1961521127$1254136028@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <38413.922841619$1254133668@xxxxxxxxxxxxxx> <h9q3tu$58j$2@xxxxxxxxxxxxx> <22297.1961521127$1254136028@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20090812)
Leo Krüger wrote:

thanks fort the fast response. Sadly that didn't help.
pciback.permissive was already passed to dom0 kernel. I additionaly added
the device to

Still the same error.

Heres a more detailed output of lspci in dom0:

debserv:~# lspci -vv -n -s 03:00.0
03:00.0 0280: 168c:0024 (rev 01)
        Subsystem: 106b:0087
        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 A routed to IRQ 18
        Region 0: Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
                Address: 00000000  Data: 0000
        Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<512ns, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <512ns, L1 <64us
                        ClockPM- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
        Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
                Vector table: BAR=0 offset=00000000
                PBA: BAR=0 offset=00000000
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Virtual Channel <?>
        Kernel driver in use: ath9k
        Kernel modules: ath9k

I added 0280: 168c:0024 to xend-pci-permissive.sxp, is this right?
What about adding the device to xend-pci-quirks.sxp? It seems as if this
file is for devices which need access to configuration space. How do I know
which config space fields the device needs access to?


Please verify if the error message is related to loading the driver at all, i.e. watch xm dmesg before/after you try to load the ath9k driver.

Also have a look at dom0 (non-xm) dmesg, because this is usually the place where the need for permissive/quirks is logged.

Best regards,

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>