All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Wei Liu <liuw@liuw.name>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: netback Oops then xenwatch stuck in D state
Date: Mon, 04 Feb 2013 11:12:43 -0500	[thread overview]
Message-ID: <510FDDFB.1040102@theshore.net> (raw)
In-Reply-To: <CAOsiSVVyNU8GiJZ1km805nL3+UrrE-4J1Wo_UKjMvOiyzpr-xw@mail.gmail.com>

On 2/1/13 8:01 PM, Wei Liu wrote:
> Dose your Dom0 has very limited RAM?
>
> Just happened to fix a bug related to OOM not getting handled correctly.
>
> http://lists.xen.org/archives/html/xen-devel/2013-01/msg02549.html

I'm not sure if it was under abnormal memory pressure.  We've tuned 
things quite a bit to not swap thrash under worst-case conditions.  But 
things happen.

If this is a likely culprit then we'll rebuild with this patch and we'll 
give it a go.  Thanks!

-Chris

  reply	other threads:[~2013-02-04 16:12 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 [this message]
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
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=510FDDFB.1040102@theshore.net \
    --to=caker@theshore.net \
    --cc=liuw@liuw.name \
    --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.