xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	ehabkost@redhat.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"wei.wang2@amd.com" <wei.wang2@amd.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	Keir Fraser <keir.xen@gmail.com>,
	Santosh Jodh <Santosh.Jodh@citrix.com>
Subject: Re: Using debug-key 'o:  Dump IOMMU p2m table, locks up machine
Date: Tue, 2 Oct 2012 16:09:07 -0400	[thread overview]
Message-ID: <20121002200907.GC668@phenom.dumpdata.com> (raw)
In-Reply-To: <5045E55A02000078000986E4@nat28.tlf.novell.com>

On Tue, Sep 04, 2012 at 10:26:18AM +0100, Jan Beulich wrote:
> >>> On 04.09.12 at 10:13, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> > Hmm don't know how to get the file/line, only thing i have found is:
> > 
> > serveerstertje:/boot# gdb xen-syms-4.2.0-rc4-pre
> > GNU gdb (GDB) 7.0.1-debian
> > Copyright (C) 2009 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> > and "show warranty" for details.
> > This GDB was configured as "x86_64-linux-gnu".
> > For bug reporting instructions, please see:
> > <http://www.gnu.org/software/gdb/bugs/>...
> > Reading symbols from /boot/xen-syms-4.2.0-rc4-pre...done.
> > (gdb) x/i 0xffff82c48015c9ee
> > 0xffff82c48015c9ee <context_switch+916>:        mov    %edx,%gs
> > (gdb)
> 
> I'm not really a gdb expert, so I don't know off the top of my
> head either. I thought I said in a previous reply that people
> generally appear to use the addr2line utility for that purpose.
> 
> But the disassembly already tells us where precisely the
> problem is: The selector value (0x0063) attempted to be put
> into %gs is apparently wrong in the context of the current
> GDT. Now, that's GDT_ENTRY_TLS_MIN on the Linux side,
> and ought to be valid. I'm surprised the guest (and the current
> process in it) survives this (as the failure here results in a failsafe
> callback into the guest).
> 
> Looking at the Linux side of things, this has been that way
> forever, and I think has always been broken: On x86-64, it
> should also clear %gs here (since 32-bit processes use it for
> their TLS, and there's nothing wrong for a 64-bit process to put
> something in there either), albeit not via loadsegment(), but
> through xen_load_gs_index(). And I neither see why on 32-bit
> it only clears %gs - %fs can as much hold a selector that might
> get invalidated with the TLS descriptor updates. Eduardo,
> Jeremy, Konrad?

How is it on the SLES side? Do you set/restore all of the segment
registers?
> 
> Jan

  reply	other threads:[~2012-10-02 20:09 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31 21:45 Using debug-key 'o: Dump IOMMU p2m table, locks up machine Sander Eikelenboom
2012-08-31 22:24 ` Santosh Jodh
2012-08-31 22:42   ` Sander Eikelenboom
2012-08-31 22:57     ` Santosh Jodh
2012-08-31 23:16       ` Sander Eikelenboom
2012-08-31 23:58         ` Santosh Jodh
2012-09-01  0:42         ` Santosh Jodh
2012-09-03  8:14           ` Jan Beulich
2012-09-01  2:01         ` Keir Fraser
2012-09-01 17:03           ` Santosh Jodh
2012-09-01 19:13             ` Keir Fraser
2012-09-02  2:08               ` Santosh Jodh
2012-09-02  7:13                 ` Keir Fraser
2012-09-02  7:19                   ` Keir Fraser
2012-09-02  8:43               ` Sander Eikelenboom
2012-09-02 14:58                 ` Keir Fraser
2012-09-02 15:14                   ` Sander Eikelenboom
2012-09-03 15:20                     ` Wei Wang
2012-09-04  8:21                       ` Sander Eikelenboom
2012-09-04 16:43                       ` Sander Eikelenboom
2012-09-05 10:14                         ` Jan Beulich
2012-09-05 10:25                           ` Sander Eikelenboom
2012-09-05 10:40                             ` Jan Beulich
2012-09-05 10:48                               ` Sander Eikelenboom
2012-09-05 11:41                                 ` Jan Beulich
2012-09-05 12:11                                   ` Sander Eikelenboom
2012-09-05 14:15                               ` Wei Wang
2012-09-05 15:05                                 ` Jan Beulich
2012-09-05 12:48                             ` Wei Wang
2012-09-05 12:30                         ` Wei Wang
2012-09-03  8:21                 ` Jan Beulich
2012-09-03  8:33                   ` Sander Eikelenboom
2012-09-03  9:05                     ` Jan Beulich
2012-09-04  7:08                   ` Sander Eikelenboom
2012-09-04  7:46                     ` Jan Beulich
2012-09-04  8:13                       ` Sander Eikelenboom
2012-09-04  9:26                         ` Jan Beulich
2012-10-02 20:09                           ` Konrad Rzeszutek Wilk [this message]
2012-10-03 13:12                             ` Jan Beulich
2012-10-02 20:54                           ` Matt Wilson
2012-09-20  8:08                         ` Jan Beulich
2012-09-28 14:08                           ` Sander Eikelenboom
2012-09-28 21:26                           ` Jeremy Fitzhardinge
2012-10-02 20:08                             ` Konrad Rzeszutek Wilk
2012-09-02  7:42 ` Keir Fraser
2012-09-04  6:35   ` Jan Beulich
2012-09-04  6:52     ` Sander Eikelenboom
2012-09-04  7:01       ` Keir Fraser
2012-09-04  6:59     ` Keir Fraser
2012-09-04  7:55       ` Jan Beulich
2012-09-04  8:04         ` Keir Fraser
2012-09-04  8:11           ` Keir Fraser
2012-09-04  8:20             ` Sander Eikelenboom
2012-09-04  8:38             ` Jan Beulich
2012-09-04  8:54               ` Keir Fraser
2012-09-04  9:40                 ` Jan Beulich
2012-09-04 13:29                   ` 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=20121002200907.GC668@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=Santosh.Jodh@citrix.com \
    --cc=ehabkost@redhat.com \
    --cc=jeremy@goop.org \
    --cc=keir.xen@gmail.com \
    --cc=linux@eikelenboom.it \
    --cc=wei.wang2@amd.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).