From: Keir Fraser <keir@xensource.com>
To: Jacek Konieczny <jajcus@jajcus.net>, xen-devel@lists.xensource.com
Subject: Re: netfront: rx->offset: 12, size: 4294967295
Date: Fri, 01 Jun 2007 15:22:03 +0100 [thread overview]
Message-ID: <C285EA1B.FDDE%keir@xensource.com> (raw)
In-Reply-To: <20070601140510.GC9591@jajo.eggsoft.pl>
On 1/6/07 15:05, "Jacek Konieczny" <jajcus@jajcus.net> 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
next prev parent reply other threads:[~2007-06-01 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 14:05 netfront: rx->offset: 12, size: 4294967295 Jacek Konieczny
2007-06-01 14:22 ` Keir Fraser [this message]
2007-06-01 16:56 ` Jacek Konieczny
2007-06-01 17:11 ` Jacek Konieczny
2007-06-01 17:38 ` Keir Fraser
2007-06-01 19:01 ` Jacek Konieczny
2007-06-02 10:13 ` Keir Fraser
2007-06-02 18:49 ` Jacek Konieczny
2007-06-03 8:33 ` Keir Fraser
2007-06-03 11:51 ` Jacek Konieczny
2007-06-04 12:40 ` Jacek Konieczny
2007-06-04 12:52 ` Keir Fraser
2007-06-04 14:05 ` Jacek Konieczny
2007-06-04 14:08 ` Keir Fraser
2007-06-06 0:30 ` Mark Williamson
2007-06-05 21:48 ` Herbert Xu
2007-06-05 21:57 ` Mark Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C285EA1B.FDDE%keir@xensource.com \
--to=keir@xensource.com \
--cc=jajcus@jajcus.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.