From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Carl Patenaude Poulin <carl.patenaudepoulin@mail.mcgill.ca>,
xen-devel@lists.xen.org
Subject: Re: [BUG] gdbsx crashes Xen
Date: Thu, 11 Feb 2016 16:35:09 +0000 [thread overview]
Message-ID: <56BCB83D.8040106@citrix.com> (raw)
In-Reply-To: <CA+v+Np+B8NdxWy4A2Bcyat29rT+DAqYOOUeOjCoO48yXo7urZQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
On 11/02/16 16:25, Carl Patenaude Poulin wrote:
> Hey folks,
>
> With gdbsx running, Running `gdb -ex "target remote localhost:9999"
> crashes Xen and reboots the server.
>
> Example session: http://i.imgur.com/UXh3RCy.png
>
> Minimal reproduction: https://github.com/lilred/xen-crash-repro
>
> Top line of `xl dmesg`:
>
> Xen version 4.6.0 (root@CS.McGill.CA <mailto:root@CS.McGill.CA>)
> (gcc (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010) debug=y Mon Dec 28
> 21:34:16 EST 2015
>
> Output of `lsb_release -a`:
>
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 15.10
> Release: 15.10
> Codename: wily
>
> I can provide more information if you tell me what to look for. Also,
> I would LOVE a work-around.
At the very minimum, you need to set up a serial console and capture the
panic log.
Are you on Broadwell hardware by any chance? I fixed a SMAP violation
in that hypercall a little while ago.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2334 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-11 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 16:25 [BUG] gdbsx crashes Xen Carl Patenaude Poulin
2016-02-11 16:35 ` Andrew Cooper [this message]
2016-02-27 3:26 ` Carl Patenaude Poulin
2016-02-29 11:22 ` Andrew Cooper
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=56BCB83D.8040106@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=carl.patenaudepoulin@mail.mcgill.ca \
--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.