From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Christophe Saout <christophe@saout.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: new netfront and occasional receive path lockup
Date: Mon, 23 Aug 2010 12:04:17 -0400 [thread overview]
Message-ID: <20100823160417.GA19344@phenom.dumpdata.com> (raw)
In-Reply-To: <1282573612.7881.2.camel@leto.intern.saout.de>
On Mon, Aug 23, 2010 at 04:26:52PM +0200, Christophe Saout wrote:
> Hi yet again,
>
> [not quoting everything again]
>
> I finally managed to trigger the issue on the test VM, which is now
> stuck in that state since last night and can be inspected. Apparently
> the tx ring on the netback side is full, since every packet sent is
> immediately dropped (as seen from ifconfig output). No interrupts
> moving on the guest.
What is the kernel and hypervisor in Dom0? And what is it in DomU?
>
> Still I'm wondering what would be the best course of action trying to
> debug this now. Should I have compiled some debugger into the
> hypervisor? (gdbsx apparently needs that)
Sure. An easier path might be to do 'xm debug-keys q' which should
trigger the debug irq handler. In DomU that should print out all of the
event channel bits which we can analyze that and see if the
proper bits are not set (and hence the IRQ handler isn't picking up
from the ring buffer).
next prev parent reply other threads:[~2010-08-23 16:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 16:43 new netfront and occasional receive path lockup Christophe Saout
2010-08-22 18:37 ` Christophe Saout
2010-08-24 0:53 ` Jeremy Fitzhardinge
2010-08-23 14:26 ` Christophe Saout
2010-08-23 16:04 ` Konrad Rzeszutek Wilk [this message]
2010-08-23 17:09 ` Christophe Saout
2010-08-24 0:46 ` Jeremy Fitzhardinge
2010-08-25 0:51 ` Xu, Dongxiao
2010-09-09 18:50 ` Pasi Kärkkäinen
2010-09-10 0:55 ` Jeremy Fitzhardinge
2010-09-10 1:45 ` Xu, Dongxiao
2010-09-10 2:25 ` Jeremy Fitzhardinge
2010-09-10 2:37 ` Xu, Dongxiao
2010-09-10 2:42 ` Jeremy Fitzhardinge
2010-09-12 1:00 ` Gerald Turner
2010-09-12 8:55 ` Jeremy Fitzhardinge
2010-09-12 17:23 ` Pasi Kärkkäinen
2010-09-12 22:40 ` Gerald Turner
2010-09-13 0:03 ` Gerald Turner
2010-09-13 0:54 ` Xu, Dongxiao
2010-09-13 2:12 ` Gerald Turner
2010-09-13 2:34 ` Xu, Dongxiao
2010-09-13 4:38 ` Gerald Turner
2010-09-13 16:01 ` Gerald Turner
2010-09-13 16:08 ` Pasi Kärkkäinen
2010-09-13 19:36 ` Jeremy Fitzhardinge
2010-09-14 8:25 ` Ian Campbell
2010-09-14 17:54 ` Jeremy Fitzhardinge
2010-09-14 18:44 ` Pasi Kärkkäinen
2010-09-15 9:46 ` Ian Campbell
2010-09-14 0:26 ` Xu, Dongxiao
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=20100823160417.GA19344@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=christophe@saout.de \
--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.