xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Armin Zentai <armin.zentai@ezit.hu>
To: Zoltan Kiss <zoltan.kiss@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Trying to unmap invalid handle! pending_idx: @ drivers/net/xen-netback/netback.c:998 causes kernel panic/reboot
Date: Sun, 20 Jul 2014 19:20:37 +0200	[thread overview]
Message-ID: <53CBFA65.9000209@ezit.hu> (raw)
In-Reply-To: <53C82157.9080007@citrix.com>

Hi!

On 17/07/14 21:17, Zoltan Kiss wrote:
> Hi,
>
> I've just submitted 2 patch series to xen-devel, one is for the net tree
> (with multiqueue) and one for 3.15. I believe the first two patch in the
> series should address this problem, the another two is for related
> problems. Armin, can you test all four of them together?
>
> Thanks,
>
> Zoltan
>
> p.s.: if you have the test setup running with increased loglevel, it
> would be good to see the result of that, as it can confirm that it is
> the problem I've solved in those patches

I'll compile the patches at next week, and I'll post the test results.

It's a live service, not a developers' playground, so its make the 
testing harder. We've moved back to 3.10.43-11 from the Xen4CentOS 
repository, instead of using a self-compiled kernel. The problem has 
been solved (I think), no crash over 5 days.

BEfore we're moving back the problematic VMs to the old kernel, we've 
cloned 2 of them, and running them on a HV, that runs the 3.15 kernel, 
with debug logging enabled. These VMs produced only one HV crash after 
the cloning, but we had no usable logs. It happened at night, and we 
were contiously getting very high load alerts from the HV, and after 
some minutes we've lost the connection to it, and to every VM on it. 
We've check it via KVM, and we found it continously posting the Draining 
TX queue message for all vifs. We only can do a hard reset on it, the 
logs were remain intact, no releated log entry have found in them. The 
netconsole module remained useless too, no messages has been forwarded 
after the _crash_.

So I'll apply your patches, and wait a week or two.

  reply	other threads:[~2014-07-20 17:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  2:25 Trying to unmap invalid handle! pending_idx: @ drivers/net/xen-netback/netback.c:998 causes kernel panic/reboot Armin Zentai
2014-07-14  9:52 ` Wei Liu
2014-07-14 10:53   ` Armin Zentai
2014-07-14 11:15     ` Wei Liu
2014-07-14 11:54 ` Zoltan Kiss
2014-07-14 12:07   ` Zoltan Kiss
2014-07-14 12:27     ` Zoltan Kiss
2014-07-14 12:14   ` Armin Zentai
2014-07-14 15:30     ` Zoltan Kiss
2014-07-14 21:15       ` Armin Zentai
2014-07-15  9:32         ` Wei Liu
2014-07-17 19:17     ` Zoltan Kiss
2014-07-20 17:20       ` Armin Zentai [this message]
2014-07-21 10:24         ` Zoltan Kiss

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=53CBFA65.9000209@ezit.hu \
    --to=armin.zentai@ezit.hu \
    --cc=xen-devel@lists.xen.org \
    --cc=zoltan.kiss@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).