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: janprunk@gmail.com, david.vrabel@citrix.com,
	george.dunlap@citrix.com, xen-devel@lists.xen.org
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Mon, 25 Jul 2016 12:42:39 +0200	[thread overview]
Message-ID: <b81918f6-5510-51e2-37da-596da185d504@andreas-ziegler.de> (raw)
In-Reply-To: <20160725102316.GK1008@citrix.com>

> On Mon, Jul 25, 2016 at 11:38:20AM +0200, Ingo Jürgensmann wrote:
>> On 22.07.2016 12:21, Ingo Jürgensmann wrote:
>>> On 22.07.2016 11:03, Ingo Jürgensmann wrote:
>>>
>>>> In the meanwhile, I activated IPv6 again on Tuesday evening and today
>>>> the server crashed again some minutes ago. Here's the output from
>>>> netconsole:
>>> ... and the second subsequent crash:
>>
>> ... and another crash below...
>>
>> But in the meanwhile, I wonder if anyone except Andreas and I has some
>> interest in fixing this issue, as there were absolutely no comments or
>> feedback on my previous mails. Quite disappointing. :-/
>>
> 
> 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.
> 
[...]
> Your report and the debian report suggested that Dom0 kernel is less
> likely to be the culprit because you've tried different Dom0 kernels.

yes we did. but nothing newer than 3.16 so far, we could try that, too.


> 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.

ok, we'll try!


> As for hardware, it would be worth trying whether this issue happens on
> other hardware platform.

as i wrote earlier on the list, we have two platforms which only have
the Intel Xeon CPU in common, nothing else - and even that is from a
very different generation.


Andreas.

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

  reply	other threads:[~2016-07-25 10:42 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 [this message]
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
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=b81918f6-5510-51e2-37da-596da185d504@andreas-ziegler.de \
    --to=ml@andreas-ziegler.de \
    --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).