[Xen-bugs] [Bug 554] New: PCI delegation works, access to the delegated NIC doesn't

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=554

           Summary: PCI delegation works, access to the delegated NIC
                    doesn't
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: alex.wilms@xxxxxxxxxxxxx


I delegated successfully my NIC to a domU, but access to it from domU is not 
possible. Device apperas, but access to it doesn't work. Delegating my USB 
controllers e.g. works flawlessly.

Partly output of my dmesg:
tg3.c:v3.49 (Feb 2, 2006)
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth1: Tigon3 [partno(BCM95789) rev 4101 PHY(5750)] (PCI Express) 
10/100/1000Base
T Ethernet 00:30:1b:b9:bf:d8
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76180000]
tg3: tg3_reset_hw timed out for eth1, firmware will not restart magic=00000000
tg3: tg3_reset_hw timed out for eth1, firmware will not restart magic=00000000

ifconfig eth2:
eth2      Link encap:Ethernet  HWaddr 00:30:1B:B9:BF:D8
          BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16

"ifconfig eth2 up" hangs and tells me after a few seconds that there is no 
such device.

lspci:
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5789 Gigabit 
Ethernet PCI Express (rev 11)

hg identify
2d87e2747973 tip

Kernel: 2.6.16-rc5

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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