All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Julien Grall <julien@xen.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Tentative fix for dom0 boot problem
Date: Wed, 22 Jun 2022 14:13:41 +0200	[thread overview]
Message-ID: <bc8899d7-0300-8640-57d9-52c2a1bf599c@suse.com> (raw)
In-Reply-To: <e32a84bf-ad49-da95-4a19-61872c2ff7e0@xen.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 2754 bytes --]

On 22.06.22 12:50, Julien Grall wrote:
> 
> 
> On 22/06/2022 11:45, Juergen Gross wrote:
>> Julien,
> 
> Hi Juergen,
> 
>> could you please test the attached patches?
> 
> I am getting the following error:
> 
> (XEN) d0v0 Unhandled: vec 14, #PF[0003]
> (XEN) Pagetable walk from ffffffff84001000:
> (XEN)  L4[0x1ff] = 000000046c004067 0000000000004004
> (XEN)  L3[0x1fe] = 000000046c003067 0000000000004003
> (XEN)  L2[0x020] = 000000046c024067 0000000000004024
> (XEN)  L1[0x001] = 001000046c001025 0000000000004001

Hmm, from this data I guess this was a write to a page table.

> (XEN) domain_crash_sync called from entry.S: fault at ffff82d040325906 
> x86_64/entry.S#create_bounce_frame+0x15d/0x177
> (XEN) Domain 0 (vcpu#0) crashed on cpu#1:
> (XEN) ----[ Xen-4.17-unstable  x86_64  debug=y  Tainted:   C    ]----
> (XEN) CPU:    1
> (XEN) RIP:    e033:[<ffffffff832a3481>]

Can you please find out the associated statement?

> (XEN) RFLAGS: 0000000000000206   EM: 1   CONTEXT: pv guest (d0v0)
> (XEN) rax: 0000000000000000   rbx: ffffffff84000000   rcx: 000000000002b000
> (XEN) rdx: ffffffff84000000   rsi: ffffffff84000000   rdi: ffffffff84001000
> (XEN) rbp: 0000000000000000   rsp: ffffffff82a03e60   r8:  0000000000000000
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
> (XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
> (XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 00000000003426e0
> (XEN) cr3: 000000046c001000   cr2: ffffffff84001000
> (XEN) fsb: 0000000000000000   gsb: ffffffff83271000   gss: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
> (XEN) Guest stack trace from rsp=ffffffff82a03e60:
> (XEN)    000000000002b000 0000000000000000 0000000000000003 ffffffff832a3481
> (XEN)    000000010000e030 0000000000010006 ffffffff82a03ea8 000000000000e02b
> (XEN)    0000000000000000 ffffffff832ae884 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffffffff832a317f 0000000000000000

Further analysis might be easier if you can supply function + displacement for
any text segment addresses on the stack.

BTW, I could boot the kernel with my patches as Dom0 without any problem. OTOH
it booted even without the patches. :-)


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-06-22 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 10:45 Tentative fix for dom0 boot problem Juergen Gross
2022-06-22 10:50 ` Julien Grall
2022-06-22 12:13   ` Juergen Gross [this message]
2022-06-22 13:20     ` Julien Grall
2022-06-22 14:21       ` Juergen Gross

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=bc8899d7-0300-8640-57d9-52c2a1bf599c@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien@xen.org \
    --cc=xen-devel@lists.xenproject.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.