From: Wei Liu <wei.liu2@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Jan Prunk <janprunk@gmail.com>, Wei Liu <Wei.Liu2@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Kernel panic on Xen virtualisation in Debian
Date: Fri, 8 Jul 2016 12:14:23 +0100 [thread overview]
Message-ID: <20160708111423.GQ416@citrix.com> (raw)
In-Reply-To: <CAFLBxZYEMSkJHcVYcMs9YeqS58bhXETfS5n3odgemp+OVKMEMg@mail.gmail.com>
On Wed, Jul 06, 2016 at 03:14:15PM +0100, George Dunlap wrote:
> On Mon, Jul 4, 2016 at 7:06 PM, Jan Prunk <janprunk@gmail.com> wrote:
> > Hello !
> >
> > I am posting Xen virtualisation bug links to this e-mail address,
> > because I wasn't able to find the Xen specific bugtracker list.
> > This bug has been discovered in 2015 and so far it hasn't been
> > resolved through the Debian/Kernel bug lists. I submit the
> > links to bug reports for you.
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804079
>
> The serial log at the bottom looks like there was a crash in the ipv6
> handling as the result of a packet delivery, perhaps? David / Wei, do
> you have any ideas? Not sure who else has worked on the netback side
> of things.
>
The original bug report showed that there was a exception in the middle
of memcpy instruction while the latest log showed that the exception
could potentially be somewhere else. Both logs showed that the
exception took place when ipv6 was involved.
If Jan can come up with a reliable repro I might be able to have a look.
Wei.
> -George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-08 11:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 18:06 Kernel panic on Xen virtualisation in Debian Jan Prunk
2016-07-06 14:14 ` George Dunlap
2016-07-08 11:14 ` Wei Liu [this message]
2016-07-08 12:22 ` Jan Prunk
2016-07-09 22:29 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
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
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=20160708111423.GQ416@citrix.com \
--to=wei.liu2@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=janprunk@gmail.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).