xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Kevin.Mayer@gdata.de, xen-devel@lists.xen.org
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	Tamas K Lengyel <tamas@tklengyel.com>,
	George Dunlap <George.Dunlap@citrix.com>
Subject: Re: Xen 4.6.1 crash with altp2m enabled by default
Date: Fri, 29 Jul 2016 11:57:08 +0200	[thread overview]
Message-ID: <1469786228.5501.30.camel@citrix.com> (raw)
In-Reply-To: <5C9C3B9BEF1B354596EAE3D6800D876B2D31F567@e2.gdata.de>


[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]

On Fri, 2016-07-29 at 07:33 +0000, Kevin.Mayer@gdata.de wrote:
> Hi guys
>  
Hi,

I'm pretty much just Cc-ing maintainers/key people, to see if they have
ideas.

Only one thing. Since you are rebuilding Xen anyway, I think it could
be helpful to try a debug build, and post the dump it will produce.

> (XEN) ----[ Xen-4.6.1  x86_64  debug=n  Not tainted ]----
>
I.e., this would need to become debug=y.

Since you said you're using 4.6.x, I think putting "debug=y" in a
.config file (and then rebuilding and reinstalling, of course) should
be enough.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-07-29  9:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  7:33 Xen 4.6.1 crash with altp2m enabled by default Kevin.Mayer
2016-07-29  9:57 ` Dario Faggioli [this message]
2016-07-29 10:05 ` Andrew Cooper
2016-08-02 11:45   ` Kevin.Mayer
2016-08-02 12:34     ` Jan Beulich
2016-08-03 13:24       ` Kevin.Mayer
2016-08-03 13:54         ` Jan Beulich
2016-08-04 15:08           ` Kevin.Mayer
2016-08-04 15:35             ` Jan Beulich
2016-08-05 12:51               ` Xen 4.6.1 crash with altp2m enabled bydefault Kevin.Mayer
2016-08-05 14:48                 ` Jan Beulich
2016-08-08  9:48                   ` Xen 4.6.1 crash with altp2m enabledbydefault Kevin.Mayer
2016-08-08 10:29                     ` Jan Beulich
2016-08-19 10:01                       ` Kevin.Mayer
2016-08-22 11:58                         ` Andrew Cooper
2016-08-22 12:22                           ` Kevin.Mayer
2016-09-07  8:35                           ` Kevin.Mayer
2016-09-21 14:18                           ` Kevin.Mayer
2016-09-22 10:13                             ` Jan Beulich
     [not found]                               ` <5C9C3B9BEF1B354596EAE3D6800D876B2DCF7138@e3.gdata.de>
     [not found]                                 ` <57E405970200007800111B26@prv-mh.provo.novell.com>
     [not found]                                   ` <5C9C3B9BEF1B354596EAE3D6800D876B2DCF7254@e3.gdata.de>
2016-09-26  9:20                                     ` Xen 4.6.1 crash with altp2menabledbydefault Jan Beulich

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=1469786228.5501.30.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Kevin.Mayer@gdata.de \
    --cc=tamas@tklengyel.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 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).