xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ziegler <ml@andreas-ziegler.de>
To: "Wei Liu" <wei.liu2@citrix.com>,
	"Ingo Jürgensmann" <ij@2013.bluespice.org>
Cc: 804079@bugs.debian.org, janprunk@gmail.com,
	xen-devel@lists.xen.org, george.dunlap@citrix.com,
	david.vrabel@citrix.com
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Fri, 29 Jul 2016 13:45:55 +0200	[thread overview]
Message-ID: <5f3d24c5-0851-c661-99a1-b484e66613a2@andreas-ziegler.de> (raw)
In-Reply-To: <20160725131304.GL27082@citrix.com>

Hello Wei,

we tried with kernel 4.6 now, the crashed happened again, though.

next we want to try the Xen debug build, but we couldn't find any
information on how to enable debug for the build, perhaps you could give
us a hint.

- Andreas


-------- Original-Nachricht --------
Betreff: Re: [Xen-devel] Kernel panic on Xen virtualisation in Debian
Von: Wei Liu <wei.liu2@citrix.com>
An: Ingo Jürgensmann <ij@2013.bluespice.org>
Datum: 25.7.2016, 15:13:06

> On Mon, Jul 25, 2016 at 01:41:41PM +0200, Ingo Jürgensmann wrote:
>> On 25.07.2016 12:23, Wei Liu wrote:
>>
>> First, thank you for replying! Very much appreciated! :)
>>
>>> I did skim your emails. But the oops was happening in memcpy+0x6 which
>>> indicated it came back to the origin question why would it got an
>>> exception there.
>>>
>>> Just by staring at the code doesn't get me anywhere. Without a concrete
>>> reproduction of the issue, I'm afraid I can't provide more input here.
>>
>> Well, from my point of view, it happens quite often when accessing the
>> server via SSH. For example today it crashed when I wanted to add something
>> and after I clicked into putty and typed the first char. In another putty,
>> where I have my netconsole log open, I instantly saw the oops.
>>
>> But what exactly causing these kinds of reboots, I'm clueless as you too.
>> Only that I do experience far more frequent crashes when accessing the
>> server from workplace via putty on Windows than via SSH on OSX or Debian
>> Linux.
>>
>>> There are several moving parts:
>>> 0. Hardware
>>> 1. Xen hypervisor
>>> 2. Dom0 kernel
>>> Your report and the debian report suggested that Dom0 kernel is less
>>> likely to be the culprit because you've tried different Dom0 kernels.
>>
>> As just written in the other mail, I already tried kernel 4.5 from
>> backports. Still crashing.
>>
>>> As for Xen, not sure if you would be up for trying a debug build from
>>> source tree. That would help provide information on whether this is a
>>> bug in Xen or not.
>>
>> Will try to build from Debian source, but how to enable debug build?
>>
> 
> I was thinking about building directly from xen.git.
> 
> http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source
> 
> Probably try the Xen 4.7 release.
> 
> Wei.
> 
>> -- 
>> Ciao...          //        http://blog.windfluechter.net
>>       Ingo     \X/     XMPP: ij@jabber.windfluechter.net
>>
>>
>> gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc

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

  reply	other threads:[~2016-07-29 11:45 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 [this message]
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
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=5f3d24c5-0851-c661-99a1-b484e66613a2@andreas-ziegler.de \
    --to=ml@andreas-ziegler.de \
    --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=wei.liu2@citrix.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).