[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Tentative fix for dom0 boot problem
Hi Juergen, On 22/06/2022 13:13, Juergen Gross wrote: 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 0000000000004001Hmm, 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? arch/x86/kernel/head64.c:433 This is the memset() for __brk_base. (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 0000000000000000Further analysis might be easier if you can supply function + displacement forany text segment addresses on the stack. ffffffff832ae884: arch/x86/include/asm/text-patching.h:112 ffffffff832a317f: arch/x86/kernel/head64.c:325 BTW, I could boot the kernel with my patches as Dom0 without any problem. OTOHit booted even without the patches. :-) So I have tried with two different compilers (GCC 7.3.1 and GCC 10.2.1) and hit the same error. This would suggest this is related to my .config. You can find it in [1] if you want to reproduce it yourself. Cheers, [1] https://pastebin.com/xityGDN9 -- Julien Grall
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |