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


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

To: "'Christian Tramnitz'" <chris.ace@xxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: AW: [Xen-users] Re: AW: Re: PCI passthrough problem
From: Leo Krüger <leo.krueger@xxxxxxxxxxxxx>
Date: Mon, 28 Sep 2009 13:43:11 +0200
Delivery-date: Mon, 28 Sep 2009 04:44:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <h9q6pc$58j$3@xxxxxxxxxxxxx>
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> <h9q6pc$58j$3@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpAL2luMmAy+MWXR4OZBk/VARcU9QAANi0g
The following error message always appears in xm dmesg when I load ath9k.

(XEN) mm.c:740:d1 Non-privileged (1) attempt to map I/O space 000febf0

The only thing regarding the wlan-card in dom0 dmesg is the following:

[    1.541544] pci 0000:03:00.0: reg 10 64bit mmio: [0xfebf0000-0xfebfffff]
[    1.541544] pci 0000:03:00.0: supports D1
[    1.541544] pci 0000:03:00.0: PME# supported from D0 D1 D3hot
[    1.541544] pci 0000:03:00.0: PME# disabled

And when I start the domU:

[  115.707617] pciback 0000:03:00.0: enabling device (0000 -> 0002)
[  115.707826] pciback 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ
[  115.708492] pciback 0000:03:00.0: setting latency timer to 64

Greetings Leo

-----Ursprüngliche Nachricht-----
Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von Christian
Gesendet: Montag, 28. September 2009 13:31
An: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: [Xen-users] Re: AW: Re: PCI passthrough problem

Leo Krüger wrote:
> Hi,
> thanks fort the fast response. Sadly that didn't help.
> pciback.permissive was already passed to dom0 kernel. I additionaly added
> the device to
> xend-pci-permissive.sxp.
> 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-
> 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
> PME(D0+,D1+,D2-,D3hot+,D3cold-)
>                 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-
> Unsupported-
>                         RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                         MaxPayload 128 bytes, MaxReadReq 512 bytes
>                 DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
> TransPend-
>                 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-
> CommClk+
>                         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
> which config space fields the device needs access to?
> Leo

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

Xen-users mailing list

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