From: Anthony Wright <anthony@overnetdata.com>
To: 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:36:20 +0000 (GMT) [thread overview]
Message-ID: <19758084.30.1417707380178.JavaMail.root@zimbra.overnetdata.com> (raw)
In-Reply-To: <547CB0AF.6010901@citrix.com>
> 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.
dmesg output
============
[76571.687014] vif vif-6-0 vif6.0: txreq.offset: a5e, size: 4002, end: 6656
[76571.687035] vif vif-6-0 vif6.0: fatal error; disabling device
[76571.700304] br-primary-1: port 2(vif6.0) entered disabled state
/sys/kernel/debug/xen-netback/vif6.0/io_ring_q0
===============================================
Queue 0
TX: nr_ents 256
req prod 10164 (39) cons 10127 (2) event 10126 (1)
rsp prod 10125 (base) pvt 10125 (0) event 10145 (20)
pending prod 9589 pending cons 9333 nr_pending_reqs 0
dealloc prod 8501 dealloc cons 8501 dealloc_queue 0
RX: nr_ents 256
req prod 1321 (41) cons 1280 (0) event 1 (-1279)
rsp prod 1280 (base) pvt 1280 (0) event 1281 (1)
NAPI state: 1 NAPI weight: 64 TX queue len 0
Credit timer_pending: 0, credit: 18446744073709551615, usec: 0
remaining: 18446744073678062682, expires: 0, now: 4314107964
/sys/kernel/debug/xen-netback/vif6.0/io_ring_q1
===============================================
Queue 1
TX: nr_ents 256
req prod 10106 (0) cons 10106 (0) event 10107 (1)
rsp prod 10106 (base) pvt 10106 (0) event 10107 (1)
pending prod 9573 pending cons 9317 nr_pending_reqs 0
dealloc prod 8503 dealloc cons 8503 dealloc_queue 0
RX: nr_ents 256
req prod 594 (39) cons 555 (0) event 1 (-554)
rsp prod 555 (base) pvt 555 (0) event 556 (1)
NAPI state: 1 NAPI weight: 64 TX queue len 0
Credit timer_pending: 0, credit: 18446744073709551615, usec: 0
remaining: 18446744073678038030, expires: 0, now: 4314118667
next prev parent reply other threads:[~2014-12-04 15:36 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 [this message]
2014-12-04 15:53 ` David Vrabel
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=19758084.30.1417707380178.JavaMail.root@zimbra.overnetdata.com \
--to=anthony@overnetdata.com \
--cc=david.vrabel@citrix.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.