From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: netfront: rx->offset: 12, size: 4294967295 Date: Fri, 01 Jun 2007 15:22:03 +0100 Message-ID: References: <20070601140510.GC9591@jajo.eggsoft.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070601140510.GC9591@jajo.eggsoft.pl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jacek Konieczny , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 1/6/07 15:05, "Jacek Konieczny" 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? 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. -- Keir