From: "Christopher S. Aker" <caker@theshore.net>
To: Wei Liu <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: netback Oops then xenwatch stuck in D state
Date: Mon, 11 Feb 2013 11:17:47 -0500 [thread overview]
Message-ID: <511919AB.3070001@theshore.net> (raw)
In-Reply-To: <1360583103.16636.29.camel@zion.uk.xensource.com>
On 2/11/13 6:45 AM, Wei Liu wrote:
> OK, so the guest is faulting at different offset now. It is very likely
> that there is OOM / race condition in other places. And judging from
> your two emails, I presume this bug can be reproduce steadily.
It is frequent enough to be a problem, yes. We're constantly deploying
new servers and upgrading the stack on existing ones, so testing changes
won't be a problem.
> A quick check on the xen_spinlock struct, its offset should not be
> 0x8b8. Reading the backtrace suggests that it is the netbk struct is
> gone.
Great, we've narrowed it down some.
> Do you manipulate the number of vcpus Dom0 has after it's up?
No, we do not.
Thanks,
-Chris
next prev parent reply other threads:[~2013-02-11 16:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 21:58 netback Oops then xenwatch stuck in D state Christopher S. Aker
2013-02-01 22:14 ` Andrew Cooper
2013-02-02 1:01 ` Wei Liu
2013-02-04 16:12 ` Christopher S. Aker
2013-02-04 17:37 ` Wei Liu
2013-02-10 5:30 ` Christopher S. Aker
2013-02-10 22:03 ` Christopher S. Aker
2013-02-11 11:45 ` Wei Liu
2013-02-11 16:17 ` Christopher S. Aker [this message]
2013-02-11 16:57 ` Wei Liu
2013-02-11 18:44 ` Christopher S. Aker
2013-02-12 14:59 ` Wei Liu
2013-02-12 9:58 ` Ian Campbell
2013-02-13 2:51 ` Christopher S. Aker
2013-02-13 12:47 ` Wei Liu
2013-02-13 20:12 ` Christopher S. Aker
2013-02-13 20:29 ` Wei Liu
2013-02-13 16:40 ` Jan Beulich
2013-02-13 18:24 ` Wei Liu
2013-02-13 18:37 ` Wei Liu
2013-02-13 19:20 ` David Vrabel
2013-02-13 19:39 ` Wei Liu
2013-02-13 20:17 ` Wei Liu
2013-02-14 9:11 ` Jan Beulich
2013-02-14 11:20 ` Wei Liu
2013-02-14 11:34 ` Ian Campbell
2013-02-14 11:38 ` Wei Liu
2013-02-14 11:50 ` Jan Beulich
2013-02-14 11:56 ` Wei Liu
2013-02-14 11:48 ` Jan Beulich
2013-02-14 12:13 ` Wei Liu
2013-02-14 12:33 ` Jan Beulich
2013-02-14 12:40 ` Wei Liu
2013-02-14 12:45 ` Jan Beulich
2013-02-14 15:29 ` Jan Beulich
2013-02-14 15:38 ` Wei Liu
2013-02-14 12:20 ` David Vrabel
2013-02-14 12:29 ` Wei Liu
2013-02-14 12:38 ` Ian Campbell
2013-02-14 12:47 ` David Vrabel
2013-02-14 12:55 ` Wei Liu
2013-02-14 12:39 ` Jan Beulich
2013-02-14 11:25 ` David Vrabel
2013-02-14 9:14 ` Jan Beulich
2013-02-14 9:25 ` Jan Beulich
2013-02-14 10:57 ` Ian Campbell
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=511919AB.3070001@theshore.net \
--to=caker@theshore.net \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.