From: Sander Eikelenboom <linux@eikelenboom.it>
To: "Ingo Jürgensmann" <ij@2013.bluespice.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
janprunk@gmail.com, xen-devel@lists.xen.org,
Andreas Ziegler <ml@andreas-ziegler.de>,
david.vrabel@citrix.com, george.dunlap@citrix.com
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Mon, 25 Jul 2016 14:35:47 +0200 [thread overview]
Message-ID: <301658769.20160725143547@eikelenboom.it> (raw)
In-Reply-To: <583ea722b89152bfb5fac9be517cbfc3@localhost>
Monday, July 25, 2016, 1:27:20 PM, you wrote:
> On 25.07.2016 12:51, Wei Liu wrote:
>>> [...]
>>> > 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.
>> There is a 4.5 backport kernel for Jessie. Or you can compile a Dom0
>> kernel with your config file. If you go down that route, I suggest you
>> either use the newest long term support Linux kernel (4.4 according to
>> kernel.org) or the latest stable kernel.
> I already tried kernel 4.5 from backports, but it was still crashing:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804079#39
Hi Ingo,
Couldn't this just be a more generic Linux kernel issue
with the combination of ipv6, bridging and ndisc ?
Wouldn't be the first time that a config more common on systems running Xen,
would more prominently expose a kernel bug in the networking stack.
Have you brought this up on the LKML / netdev mailinglists already ?
--
Sander
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-25 12:35 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 [this message]
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=301658769.20160725143547@eikelenboom.it \
--to=linux@eikelenboom.it \
--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=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).