All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2
Date: Fri, 18 May 2018 16:34:01 -0400	[thread overview]
Message-ID: <20180518203401.GK23713@char.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805182155160.1599@nanos.tec.linutronix.de>

On Fri, May 18, 2018 at 09:57:47PM +0200, speck for Thomas Gleixner wrote:
> On Fri, 18 May 2018, speck for Konrad Rzeszutek Wilk wrote:
> > On Fri, May 18, 2018 at 03:21:54PM +0200, speck for Greg KH wrote:
> > (XEN) Std. Loglevel: All
> > (XEN) Guest Loglevel: All
> > (XEN) Xen is relinquishing VGA console.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
> > (XEN) Freed 2048kB init memory
> > (XEN) d0v0 Unhandled general protection fault fault/trap [#13, ec=0000]
> > (XEN) domain_crash_sync called from entry.S: fault at ffff82d08036eab3 x86_64/entry.S#create_bounce_frame+0x143/0x170
> > (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> > (XEN) ----[ Xen-4.11-rc  x86_64  debug=y   Not tainted ]----
> > (XEN) CPU:    0
> > (XEN) RIP:    e033:[<ffffffff81062660>]
> > (XEN) RFLAGS: 0000000000000246   EM: 1   CONTEXT: pv guest (d0v0)
> > (XEN) rax: 0000000000000246   rbx: 0000000000000000   rcx: 0000000000000000
> > (XEN) rdx: 0000000000000000   rsi: 00000000ffffffff   rdi: 0000000000000000
> > (XEN) rbp: 0000000000000000   rsp: ffffffff82203da0   r8:  ffffffff81f727a8
> > (XEN) r9:  ffffffff82203e58   r10: 00000000ffffffff   r11: ffffffff82203e7c
> > (XEN) r12: ffffffff82203efc   r13: ffffffff82203e58   r14: 0000000000000000
> > (XEN) r15: 00000000ffffffff   cr0: 000000008005003b   cr4: 00000000003526e0
> > (XEN) cr3: 00000008a351d000   cr2: 0000000000000000
> > (XEN) fsb: 0000000000000000   gsb: ffffffff82772000   gss: 0000000000000000
> > (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> > (XEN) Guest stack trace from rsp=ffffffff82203da0:
> > (XEN)    0000000000000000 ffffffff82203e7c 0000000000000000 ffffffff81062660
> > (XEN)    000000010000e030 0000000000010046 ffffffff82203de8 000000000000e02b
> > (XEN)    0000000000000246 ffffffff810df7dc 0000000000000000 0000000000000000
> > (XEN)    ffffffff81f727a8 0000000000000246 0000000000000000 0000000000000000
> > (XEN)    ffffffff82433cc0 ffffffff82203ea8 ffffffff82203efc ffffffff82203ef4
> > (XEN)    ffffffff82203ef0 ffffffff82203f0c ffffffff810e06c5 ffffffff00000008
> > (XEN)    ffffffff82203eb8 ffffffff82203e78 0000000000000000 0000000000000000
> > (XEN)    0000000000000001 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    ffffffff82203e78 0000000000000001 ffffffff8103cb53 ffffffff82433cc0
> > (XEN)    ffffffff82203ef8 ffffffff8103cda8 ffffffff82203f00 ffffffff82203f04
> > (XEN)    ffffffff82203f08 0000000100000000 0000100000003027 0000000000000000
> > (XEN)    0000000080000008 0000000000000000 ffffffff82203f58 ffffffff82203f54
> > (XEN)    ffffffff82203f50 ffffffff82203f4c 0000000000000000 0000000000000000
> > (XEN)    ffffffff8279f2ec 0000000000000000 0000012100000000 0000000020101800
> > (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > (XEN)    0f00000060c0c748 ccccccccccccc305 cccccccccccccccc cccccccccccccccc
> > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
> > (XEN) APIC error on CPU0: 40(00)
> 
> The above is pretty useless and undecodable. So what makes Dom0 crash in a
> way that the machine needs to be rebooted? The call to get_cpu_cap()?

Yup. B/c there is no early callback installed yet and it ends up using 'cli'
> 
> If so, then I really want to understand what makes it particularly explode.

It would be best if you and Boris chatted. Let me poke him to get his GPG key in order.

> 
> Thanks,
> 
> 	tglx

  reply	other threads:[~2018-05-18 20:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  3:18 [MODERATED] [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2 konrad.wilk
2018-05-18  8:20 ` [MODERATED] " Greg KH
2018-05-18  9:02   ` Thomas Gleixner
2018-05-18 11:46   ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18  9:14 ` Thomas Gleixner
2018-05-18 11:43   ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 12:03     ` Greg KH
2018-05-18 13:21 ` Greg KH
2018-05-18 18:22   ` Konrad Rzeszutek Wilk
2018-05-18 19:57     ` Thomas Gleixner
2018-05-18 20:34       ` Konrad Rzeszutek Wilk [this message]
2018-05-18 20:40         ` [MODERATED] " Linus Torvalds
2018-05-18 21:05           ` Konrad Rzeszutek Wilk
2018-05-18 21:10             ` Linus Torvalds
2018-05-19  8:33         ` Thomas Gleixner

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=20180518203401.GK23713@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=speck@linutronix.de \
    /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.