Re: PCI passthrough issue

[Jean Baptiste Favre <xen-devel@jbfavre.org>]

Le 25/02/2011 15:40, Konrad Rzeszutek Wilk a écrit :
> On Fri, Feb 18, 2011 at 10:14:13PM +0100, Jean Baptiste Favre wrote:
>> Hello,
>> Back online after my exams :)
>>
>> Had some time to perform tests with my Debian Squeeze 32bits domU and
>> 2.6.37 kernel from experimental.
> 
> I am bit lost now.. Can you refresh my memory whether the 'copy_break'
> parameter worked or not?
Copybreak param still solve problem:
# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
__netif_receive_skb dropping skb proto 0x6aac ip summed 2
__netif_receive_skb dropping skb proto 0x620c ip summed 2
__netif_receive_skb dropping skb proto 0x6aac ip summed 2
^C
--- 10.0.0.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

root@xps-106:~# rmmod sky2
[   23.137515] sky2 0000:00:00.0: eth0: disabling interface
root@xps-106:~# modprobe sky2 copybreak=0
 sky2: driver version 1.28
 sky2 0000:00:00.0: Xen PCI enabling IRQ: 18
 xen_map_pirq_gsi: returning irq 18 for gsi 18
 sky2 0000:00:00.0: Yukon-2 EC Ultra chip revision 3
 xen_map_pirq_gsi: returning irq 55 for gsi 55
 sky2 0000:00:00.0: eth0: addr 00:1f:c6:eb:71:43
 sky2 0000:00:00.0: eth0: enabling interface
 ADDRCONF(NETDEV_UP): eth0: link is not ready
 sky2 0000:00:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow
control both
 ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@xps-106:~# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_req=1 ttl=64 time=4.09 ms
64 bytes from 10.0.0.1: icmp_req=2 ttl=64 time=0.814 ms
^C
--- 10.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.814/2.456/4.098/1.642 ms

> 
> Experimental is the stock kernel or was that a new proposed kernel?
> Where are the sources for the experimental kernel?
Kernel 2.6.37 has been installed from Debian experimental repository.
Did not have time to compile my own from vanilla sources.
Maybe will have some time this week, but not sure.


>> DomU config is:
>> *****************************************************************
>> kernel       = '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem'
>> ramdisk      = '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem'
>> #kernel       = '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem-sky2'
>> #ramdisk      = '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem-sky2'
>> builder      = 'linux'
>> memory=268
>> vcpus        = '1'
>> cpus         = '2'
>> localtime    = 0
>> serial       = 'pty'
>> boot         = 'cdn'
>> disk         = [ 'drbd:xps-106,xvda,w' ]
>> on_poweroff  = 'destroy'
>> on_reboot    = 'restart'
>> on_crash     = 'restart'
>> name         = 'xps-106'
>> hostname     = 'xps-106.clichy.jbfavre.org'
> 
> I had a box with a sky2 adapter that looked to have a similar issue but
> found the culprit to be the switch. So at this point I am having no luck
> reproducing this. Would it be possible for you to stick the kernel + dist
> image somewhere so I can try it out on my box?
As requested by you (or Ian, I don't remeber exactly), I've tried
booting the server with 32bits 2.6.37 kernel and 32bits Debian Squeeze.
Even with mem=256 boot param, everything worked fine, so I'm not sure
switch can be the culprit.

>> extra = "root=/dev/mapper/xps--106-root ro iommu=soft swiotlb=force
>> console=hvc0 xencons=tty"
> 
> Try without 'swiotlb=force' on any kernel that is PVOPS. Only the older
> ones (lenny) required that. And you don't need 'xencons=tty' either with
> PVOPS kernels.
OK, will try that.

Regards,
JB