| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
 Re: [Xen-devel] igb pciback and e1000e pciback not work.
 
To: Pasi KÃrkkÃinen <pasik@xxxxxx>, 	xen-devel@xxxxxxxxxxxxxxxxxxxFrom: èé <xnhp0320@xxxxxxxxx>Date: Mon, 6 Sep 2010 12:58:48 +0800Cc: Delivery-date: Sun, 05 Sep 2010 22:00:41 -0700Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;	h=mime-version:in-reply-to:references:from:date:message-id:subject:to	:content-type;	b=SZ/oFF7Ge7YaqW+vw7E3bv6+i4EaggS5ORcdZhH8Bil5gzRT+bE5yVBPXavGTY8BAZ	PQSDKyafOtJ7zZLDf70I0KXmZyH3HflOhhKaImTlISU+0/bO+KpsHSH7LcFbpsiCv4Es	pETa1a4fXItxgzR5ucooFfvkKR7JBUS072zLs=List-id: Xen developer discussion <xen-devel.lists.xensource.com> 
 Thank you for your advise. I update the kernel and xen to the newest version. Now both Dom0 and DomU's kernels are 2.6.32.21-xen
 
 still the e1000e driver in DomU complains about the "Detected Tx Unit Hang", but there is no kernel oops. It seems the new kernel has fixed a bug about pciback. 
 Maybe I should change theÂ/etc/xen/xend-pci-permissive.sxp and /etc/xen/xend-pci-quirks.sxp file ,because I found this in Dom0 dmesg: 
 [ Â385.007473] pciback 0000:09:00.1: Driver tried to write to a read-only configuration space field at offset 0xe8, size 2. This may be harmless, but if you have problems with your device: 
[ Â385.007475] 1) see permissive attribute in sysfs [ Â385.007475] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
 note: 09:00.0 is the pci interface I move to DomU . But I don't know how to change this. 
 I remove the e1000e driver in Dom0 , still it can't fix the problem. 
 Anyone knows about that? 
 thanks. 
 2010/9/5 Pasi KÃrkkÃinen <pasik@xxxxxx> 
On Sun, Sep 05, 2010 at 10:55:35AM +0800, ?????? wrote:>  ÂAt first I want to test the performance of pci passthrough à when it comes>  ÂI'm using Xen 4.01 and jeremy's pvops kernel, the kernel version is
 > Â Â2.6.32.18.
 
 
 > Â Âto the network card 82571EB> Â ÂIt seems to work well,Ã>
 > Â ÂI'm using the Jeremy's kernel 2.6.32.18 as DomU kernel too.
 >
 > Â ÂAnd I found if the interface is not connected, I mean the network card
 > Â Âreceives no packet, ( the network card doesn't connect to the switch ),
 > Â Âit's fine. when I connect it to a switch , I got a lot of "Detected Tx
 > Â ÂUnit Hang" in dmesg of the DomU kernel
 > Â Âand a kernel oops saying:
 >
 > Â ÂPid: 0, comm: swapper Not tained 2.6.32.18-xen #4
 > Â Âwarn_slowpath_fmt+0x41/0x50
 >
 > Â Âthe ooops image is in the attachment of this post.
 >
 > Â ÂI've checked the mailing list, some one said it's about the e1000e driver
 > Â Âwith a wrong
 > Â Âconfig of the EEPROM.
 >
 > Â ÂSo I switch to use the network card 82575EB with igb driver
 
 
 > Â Âuntil I find it can't receive any packets in DomU.Hello,> Â ÂAnd I see a lot of packets dropped when I ifconfig these interfaces.
 > Â ÂAnyone knows how to deal with this ?
 >
 
 
 
 The latest kernel version in xen/stable-2.6.32.x branch is 2.6.32.21.
 Dunno if it has any fixes that are relevant to you.
 
 Anyway, did you read: http://wiki.xensource.com/xenwiki/XenPCIpassthrough
 
 -- Pasi
 
 
 _______________________________________________
 Xen-devel mailing list
 Xen-devel@xxxxxxxxxxxxxxxxxxx
 http://lists.xensource.com/xen-devel
 
--  hepeng ICT
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |