WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Intel Quad NIC quirks

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Intel Quad NIC quirks
From: Alexander Menk <alex.menk.lists2@xxxxxxxxxxxxxx>
Date: Wed, 10 Jun 2009 12:14:42 +0300
Delivery-date: Wed, 10 Jun 2009 07:20:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=viNNwH044If2fpLA/mq31RTV6fjz0GrDqmvCOwhJrFY=; b=jYxJmYV6YkE0JLG9CFVtm6QAv3mntks9kK9s+WPHiza64NGfH1Zmc72EV+mk+ossC1 NwmVizMmX8CXlG/wtC4byRzQf7W1uuD2wwtHobF0QCSULMy/aIp/x8g0G8R0fjlT9yi7 1VGt5VSz3WrLXb3jtONsKVUVuihYwB2nikSr4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=TkEpPdxx8XZhmyeuI6q3KTN29AemZurDboE2zht+zniSm9Dd5xxp/CjnugmiII0PHI cVMFnlVPm/nikRqGBAlvjd8WV6rSvcCg4SiIyImpklvi4EzVpW9kLWQ1hRgM7vMjDBs6 OJpmhjhJiQOyH5iCegTOh5C4m4EDfKkN6Yj+I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


I added some  lines to  xend-pci-quirks.sxp in order to make the Intel
Quad NIC 82576 working. The message to check the permissive value in
syslog disappeared and I get cable connect messages inside the DomU, but
unfortunately I can not ping the device in the DomU.


Here the lspci data as requested in  xend-pci-quirks.sxp:

    (pci_config_space_fields
        # Entries are formated as follows:  
        #     <register>:<size>:<mask>
        # size is measured in bytes (1,2,4 are valid sizes)
        # mask is currently unused; use all zero's
....
         '000000a8:2:00000000'   # Intel Quad nic... no idea what
....



/etc/xen# lspci -s 10:00.1 -vv
10:00.1 Ethernet controller: Intel Corporation Device 10e8 (rev 01)
        Subsystem: Intel Corporation Device a02b
        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: 32 bytes
        Interrupt: pin B routed to IRQ 17
        Region 0: Memory at d9d40000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at da400000 (32-bit, non-prefetchable) [size=4M]
        Region 2: I/O ports at 6020 [disabled] [size=32]
        Region 3: Memory at d9d04000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot
+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000
                Masking: 00000000  Pending: 00000000
        Capabilities: [70] MSI-X: Enable- Mask- TabSize=10
                Vector table: BAR=3 offset=00000000
                PBA: BAR=3 offset=00002000
        Capabilities: [a0] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 512 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+ FLReset-
                        MaxPayload 128 bytes, MaxReadReq 4096 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- 
TransPend-
                LnkCap: Port #4, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency 
L0
<4us, L1 <64us
                        ClockPM- Suprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive-
BWMgmt- ABWMgmt-
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Device Serial Number 04-ad-38-ff-ff-21-1b-00
        Capabilities: [150] #0e
        Capabilities: [160] #10
        Kernel driver in use: pciback
        Kernel modules: igb


Regards,
Alexander


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Intel Quad NIC quirks, Alexander Menk <=