From: David Vrabel <david.vrabel@citrix.com>
To: Anthony Wright <anthony@overnetdata.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0
Date: Thu, 4 Dec 2014 15:53:22 +0000 [thread overview]
Message-ID: <54808372.8090102@citrix.com> (raw)
In-Reply-To: <19758084.30.1417707380178.JavaMail.root@zimbra.overnetdata.com>
On 04/12/14 15:36, Anthony Wright wrote:
>> On 01/12/14 14:22, David Vrabel wrote:
>> This VIF protocol is weird. The first slot contains a txreq with a
>> size
>> for the total length of the packet, subsequent slots have sizes for
>> that
>> fragment only.
>>
>> netback then has to calculate how long the first slot is, by
>> subtracting
>> all the size from the following slots.
>>
>> So something has gone wrong but it's not obvious what it is. Any
>> chance
>> you can dump the ring state when it happens?
>
> We think we've worked out how to dump the ring state, please see below.
We need the full contents of the ring which isn't currently available
via debugfs and I haven't had time to put together a debug patch to make
it available.
David
next prev parent reply other threads:[~2014-12-04 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 15:19 PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0 Anthony Wright
2014-11-28 15:23 ` Ian Campbell
2014-11-28 16:34 ` Anthony Wright
2014-12-01 14:22 ` David Vrabel
2014-12-01 15:47 ` Anthony Wright
2014-12-01 18:17 ` David Vrabel
2014-12-02 15:40 ` Anthony Wright
2014-12-04 15:36 ` Anthony Wright
2014-12-04 15:53 ` David Vrabel [this message]
2014-12-05 12:48 ` Zoltan Kiss
2014-12-05 14:16 ` David Vrabel
2014-12-08 12:03 ` David Vrabel
2014-12-09 16:46 ` Anthony Wright
[not found] <E3A471111497714D953FBC6F551B7AA7B6BD43C9@USALMELXP004.LUXGROUP.NET>
2014-12-09 22:39 ` Anthony Wright
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=54808372.8090102@citrix.com \
--to=david.vrabel@citrix.com \
--cc=anthony@overnetdata.com \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.com \
--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.