[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] netfront: rx->offset: 12, size: 4294967295


  • To: Jacek Konieczny <jajcus@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Sun, 03 Jun 2007 09:33:59 +0100
  • Delivery-date: Sun, 03 Jun 2007 01:29:54 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acelue5dLKcUGxGtEdyP/gAWy6hiGQ==
  • Thread-topic: [Xen-devel] netfront: rx->offset: 12, size: 4294967295

On 2/6/07 19:49, "Jacek Konieczny" <jajcus@xxxxxxxxxx> wrote:

> On Sat, Jun 02, 2007 at 11:13:49AM +0100, Keir Fraser wrote:
>> Well, that should certainly be new enough. When domU boots it should give a
>> message like 'device eth0 has <foo> receive path', where <foo> is copying or
>> flipping. Which mode does your domU claim to be using?
> 
> copying
> 
> Forcing it to copying (or flipping) with xennet module option doesn't
> change anything.  Maybe domU is right, but dom0 tries to use flipping
> because of some error?

Well, if that were the only problem then it's surprising that forcing flip
mode does not fix the bug. On the other hand, flip mode isn't much tested
these days.

In dom0, what output do you get from 'xenstore-ls /local/domain/<domid>'?
(where <domid> is the domain id of your domU).  There should be a line for a
node called request-rx-copy, with a value of 1. This is how domU declares to
netback that it wants to use copying mode.

If you're happy modifying C code a bit, a good place to add some printk()
tracing would be connect_rings() in drivers/xen/netback/xenbus.c. It's that
function which should read the request-rx-copy node and decide whether it is
going to use copying or flipping mode.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.