From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
M A Young <m.a.young@durham.ac.uk>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Backtrace in xen/next-2.6.38 when running guest
Date: Thu, 03 Feb 2011 12:51:21 -0800 [thread overview]
Message-ID: <4D4B1549.3070202@goop.org> (raw)
In-Reply-To: <1296722319.13091.378.camel@zakaz.uk.xensource.com>
On 02/03/2011 12:38 AM, Ian Campbell wrote:
> On Wed, 2011-02-02 at 21:41 +0000, Ian Campbell wrote:
>> On Wed, 2011-02-02 at 19:47 +0000, Jeremy Fitzhardinge wrote:
>>> On 02/02/2011 11:31 AM, Ian Campbell wrote:
>>>> 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).
>>> I merged it into next to get some exposure, but I'll happily revert and
>>> remerge as you make changes. What's your working branch?
>> Same branch but I haven't pushed an update yet.
> Updated version pushed to:
> git://xenbits.xen.org/people/ianc/linux-2.6.git upstream/dom0/backend/netback
Is that a rebase?
J
next prev parent reply other threads:[~2011-02-03 20:51 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
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 [this message]
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=4D4B1549.3070202@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--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.