From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [BUG] gdbsx crashes Xen Date: Thu, 11 Feb 2016 16:35:09 +0000 Message-ID: <56BCB83D.8040106@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6642673134239673475==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Carl Patenaude Poulin , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============6642673134239673475== Content-Type: multipart/alternative; boundary="------------060904030302090509000104" --------------060904030302090509000104 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit 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 ) > (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 --------------060904030302090509000104 Content-Type: text/html; charset="windows-1252" Content-Length: 2420 Content-Transfer-Encoding: quoted-printable
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.



Top line of `xl dmesg`:

=A0 =A0 Xen version 4.6.0 (root@CS.McGill.CA) (gcc (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010) debug=3Dy Mon Dec 28 21:34:16 EST 2015

Output of `lsb_release -a`:

=A0 =A0 No LSB modules are available.
=A0 =A0 Distributor ID: Ubuntu
=A0 =A0 Description: =A0 =A0Ubuntu 15.10
=A0 =A0 Release: =A0 =A0 =A0 =A015.10
=A0 =A0 Codename: =A0 =A0 =A0 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=3F=A0 I fixed a SMAP violation in that hypercall a little while ago.

~Andrew
--------------060904030302090509000104-- --===============6642673134239673475== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============6642673134239673475==--