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

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] netfront: rx->offset: 12, size: 4294967295
From: Jacek Konieczny <jajcus@xxxxxxxxxx>
Date: Fri, 1 Jun 2007 18:56:46 +0200
Delivery-date: Fri, 01 Jun 2007 09:54:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C285EA1B.FDDE%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070601140510.GC9591@xxxxxxxxxxxxxxx> <C285EA1B.FDDE%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.10i
On Fri, Jun 01, 2007 at 03:22:03PM +0100, Keir Fraser wrote:
> On 1/6/07 15:05, "Jacek Konieczny" <jajcus@xxxxxxxxxx> wrote:
> 
> > I recompiled the kernel again and again, with different options (of
> > course, I am not able to test all possible configurations) and still no
> > go. I am using vanilla 2.6.18 kernel patched with output of Xen's
> > 'make mkpatches' and with squashfs (it touches nothing but the
> > filesystem).
> > 
> > Any idea what may be wrong? What else may I try?
> 
> Any weird options on your dom0 or domU command lines?

Nothing, just root and console.

> Netback is sending error responses to your domUs, hence the messages you get
> from netfront in domU. Have you tried a debug build of Xen, and also
> redefine the DPRINTK() macro in netback.c to printk(KERN_ALERT)? This will
> very likely get you some tracing per packet about what is going wrong.

dom0 dmesg:

device vif3.0 entered promiscuous mode
xenbr0: port 5(vif3.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 5(vif3.0) entering forwarding state
blkback: ring-ref 8, event-channel 6, protocol 1 (unspecified, assuming
native)
blkback: ring-ref 9, event-channel 7, protocol 1 (unspecified, assuming
native)
blkback: ring-ref 10, event-channel 8, protocol 1 (unspecified, assuming
native)
Bad status -1 from grant transfer to DOM3
Bad status -1 from grant transfer to DOM3
Bad status -1 from grant transfer to DOM3
Bad status -1 from grant transfer to DOM3

xm dmesg:

(XEN) grant_table.c:877:d0 gnttab_transfer: Transferee has no reservation 
headroom (40960,40960) or provided a bad grant ref (000001e9) or is dying (0)
(XEN) grant_table.c:877:d0 gnttab_transfer: Transferee has no reservation 
headroom (40960,40960) or provided a bad grant ref (000001ea) or is dying (0)
(XEN) grant_table.c:877:d0 gnttab_transfer: Transferee has no reservation 
headroom (40960,40960) or provided a bad grant ref (000001eb) or is dying (0)

This is generated by xen 3.0.5-rc1 binary from the "Xen 3.1.0 32-bit
PAE" package.

Greets,
        Jacek

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