All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Andreas Ziegler <ml@andreas-ziegler.de>
Cc: "Ingo Jürgensmann" <ij@2013.bluespice.org>,
	george.dunlap@citrix.com, xen-devel@lists.xen.org,
	804079@bugs.debian.org, janprunk@gmail.com,
	david.vrabel@citrix.com, "Wei Liu" <wei.liu2@citrix.com>
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Tue, 29 Nov 2016 09:08:01 +0000	[thread overview]
Message-ID: <20161129090801.GQ11640@citrix.com> (raw)
In-Reply-To: <3b8aef80-c5dd-cf59-6279-14e921111ae2@andreas-ziegler.de>

On Mon, Nov 14, 2016 at 04:55:40PM +0100, Andreas Ziegler wrote:
> Hi,
> 
> few months later Ingo decided again to give it a try as he really
> doesn't want to keep ipv6 disabled in 2016.
> He tried Xen 4.8 - which didn't help, the crash reappeared.
> He then managed to build Xen with debug=y and soon it crashed with the
> following output, which looks a little bit longer than without debug:
> 
> http://paste.debian.net/895464/
> 

Entry not found -- maybe it expired... Sorry.

> If this still doesn't help, we would really appreciate more information
> on how to do proper debugging, the information we found online is either
> very old, confusing - or it's hidden very good?
> 

What sort of information did you find ? What do you need ?

Wei.

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

  reply	other threads:[~2016-11-29  9:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 22:29 Kernel panic on Xen virtualisation in Debian Andreas Ziegler
2016-07-10 13:18 ` Ingo Jürgensmann
2016-07-18 16:44   ` Andreas Ziegler
2016-07-22  9:03     ` Ingo Jürgensmann
2016-07-22 10:21       ` Ingo Jürgensmann
2016-07-25  9:38         ` Ingo Jürgensmann
2016-07-25 10:23           ` Wei Liu
2016-07-25 10:42             ` Andreas Ziegler
2016-07-25 10:50               ` Andreas Ziegler
2016-07-25 10:51               ` Wei Liu
2016-07-25 11:27                 ` Ingo Jürgensmann
2016-07-25 12:35                   ` Sander Eikelenboom
2016-07-25 11:41             ` Ingo Jürgensmann
2016-07-25 13:13               ` Wei Liu
2016-07-29 11:45                 ` Andreas Ziegler
2016-07-29 13:01                   ` Wei Liu
2016-07-29 20:17                   ` Ingo Jürgensmann
2016-08-02  9:20                     ` Wei Liu
2016-08-02 10:30                       ` Ingo Jürgensmann
2016-08-02 12:37                         ` Wei Liu
2016-11-14 15:55                           ` Andreas Ziegler
2016-11-29  9:08                             ` Wei Liu [this message]
2016-11-29 20:20                               ` Ingo Jürgensmann
2016-12-01 13:26                                 ` Wei Liu
2016-12-01 13:59                                   ` Ingo Jürgensmann
2016-12-01 14:07                                     ` Wei Liu
2016-12-01 14:50                                     ` Sander Eikelenboom
2016-07-25 10:49           ` David Vrabel
  -- strict thread matches above, loose matches on Subject: below --
2016-07-04 18:06 Jan Prunk
2016-07-06 14:14 ` George Dunlap
2016-07-08 11:14   ` Wei Liu
2016-07-08 12:22     ` Jan Prunk

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=20161129090801.GQ11640@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=804079@bugs.debian.org \
    --cc=david.vrabel@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ij@2013.bluespice.org \
    --cc=janprunk@gmail.com \
    --cc=ml@andreas-ziegler.de \
    --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 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.