All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jeremy, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Backtrace in xen/next-2.6.38 when running guest
Date: Wed, 2 Feb 2011 19:31:23 +0000	[thread overview]
Message-ID: <1296675083.20804.243.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.02.1102021908400.1034@vega1.dur.ac.uk>

On Wed, 2011-02-02 at 19:20 +0000, M A Young wrote: 
> I get backtraces from the dom0 kernel when running a guest with networking 
> (via netback) enabled such as the one below (there are some slight 
> variations but the first two lines and most of the rest of the contents 
> are the same).

> BUG: sleeping function called from invalid context at mm/page_alloc.c:2190

Thanks.

Netback for upstream is still a WIP (I wasn't expecting it to be merged
anywhere yet and have already and will continue to rebase my branch).

In particular one of the things which needs to go away for upstreaming
is the tasklet vs. kthread mode option in favour of always using a
kthread. Doing this will hopefully resolve this issue since the
allocation will no longer be in a context where sleeping is disallowed.

I you can't wait for my next post of the driver for upstream then
setting MODPARM_netback_kthread = 1 in drivers/net/xen-netback/netback.c
will have roughly the same effect.

Ian.

  reply	other threads:[~2011-02-02 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 19:20 Backtrace in xen/next-2.6.38 when running guest M A Young
2011-02-02 19:31 ` Ian Campbell [this message]
2011-02-02 19:47   ` Jeremy Fitzhardinge
2011-02-02 21:41     ` Ian Campbell
2011-02-03  8:38       ` Ian Campbell
2011-02-03 20:51         ` Jeremy Fitzhardinge
2011-02-03 21:22           ` 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=1296675083.20804.243.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=m.a.young@durham.ac.uk \
    --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.