xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni.tedesco@citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stabellini <Stefano.Stabellini@eu.citrix.com>Stefano
Subject: Re: xend segfaults when starting
Date: Wed, 4 Aug 2010 16:01:42 +0100	[thread overview]
Message-ID: <1280934102.18490.197.camel@qabil.uk.xensource.com> (raw)
In-Reply-To: <1280928422.18490.187.camel@qabil.uk.xensource.com>

On Wed, 2010-08-04 at 14:27 +0100, Gianni Tedesco wrote:
> On Wed, 2010-08-04 at 14:12 +0100, Christoph Egger wrote:
> > Hi!
> > 
> > xend causes python to segfault on startup.
> > The changeset in error is: 21904:6a0dd2c29999
> 
> There is a fix for this in:
> 
> [PATCH 1 of 6] xl: PCI code cleanups

My mistake, ignore the spam, local changes in what I thought was a
pristine tree. This is unrelated to the afore-mentioned bug.

Of course xend etc. is not using xl yet, so I am living in my own
fantasy :)

      parent reply	other threads:[~2010-08-04 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 13:12 xend segfaults when starting Christoph Egger
2010-08-04 13:27 ` Gianni Tedesco
2010-08-04 14:12   ` Christoph Egger
2010-08-04 14:55     ` Stefano Stabellini
2010-08-11 13:11       ` Ian Campbell
2010-08-13 11:58         ` Stefano Stabellini
2010-08-13 12:04           ` Christoph Egger
2010-08-18 10:44         ` Christoph Egger
2010-08-18 12:14           ` Ian Campbell
2010-08-18 12:18             ` Ian Campbell
2010-08-18 14:02             ` Christoph Egger
2010-08-18 14:59               ` Ian Campbell
2010-08-18 16:02                 ` Christoph Egger
2010-08-18 16:29                   ` Ian Campbell
2010-08-04 15:01   ` Gianni Tedesco [this message]

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=1280934102.18490.197.camel@qabil.uk.xensource.com \
    --to=gianni.tedesco@citrix.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --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 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).