* [bug]xen 4.10 + dom0 4.15 couldn't boot up @ 2018-01-29 5:28 Zhang, Xiong Y 2018-01-29 5:45 ` Juergen Gross 0 siblings, 1 reply; 8+ messages in thread From: Zhang, Xiong Y @ 2018-01-29 5:28 UTC (permalink / raw) To: Xen-devel; +Cc: Zhang, Xiong Y [-- Attachment #1.1: Type: text/plain, Size: 3453 bytes --] Today I found xen 4.10 (or staging branch) with dom0 4.15 kernel, dom0 couldn't boot up and it print the following error, is it a known issue ? (XEN) ..................................done. (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 460kB init memory (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] (XEN) Pagetable walk from 0000000000000028: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d0803530e4 x86_64/entry.S#create_bounce_frame+0x135/0x151 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.11-unstable x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff8103f78b>] (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) (XEN) rax: 0000000000000000 rbx: ffffffff81e06020 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: ffffffff82403e90 rdi: ffffffff82403e8c (XEN) rbp: ffffffff82403ec8 rsp: ffffffff82403e10 r8: ffffffff82403f00 (XEN) r9: 00000000ffffffff r10: ffffffff82403f04 r11: 0000000000000000 (XEN) r12: ffffffff82403e88 r13: ffffffff82403e78 r14: ffffffff82403e80 (XEN) r15: ffffffff82403e84 cr0: 000000008005003b cr4: 00000000003526e0 (XEN) cr3: 000000040eb66000 cr2: 0000000000000028 (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff82403e10: (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103f78b (XEN) 000000010000e030 0000000000010092 ffffffff82403e58 000000000000e02b (XEN) 0000000000000000 ffffffff826591e0 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff826591e0 ffffffff82403f04 (XEN) ffffffff82403f00 ffffffff82403efc ffffffff82403ef8 ffffffff82403f40 (XEN) ffffffff81040343 ffffffff82403f14 ffffffff82403f10 ffffffff82403f0c (XEN) ffffffff82403f08 0000000000003027 0000000000000000 0000000080000008 (XEN) 0000000000000000 ffffffff81032100 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff82403ff8 ffffffff826ac35d (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) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. (XEN) APIC error on CPU0: 40(00) (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. Xen 4.9 + dom0 4.15 is OK. Xen 4.10 + dom0 4.14 is also OK. Only Xen 4.10 + dom0 4.15 has such issue. thanks [-- Attachment #1.2: Type: text/html, Size: 9368 bytes --] [-- Attachment #2: Type: text/plain, Size: 157 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-01-29 5:28 [bug]xen 4.10 + dom0 4.15 couldn't boot up Zhang, Xiong Y @ 2018-01-29 5:45 ` Juergen Gross 2018-01-30 0:33 ` Zhang, Xiong Y 0 siblings, 1 reply; 8+ messages in thread From: Juergen Gross @ 2018-01-29 5:45 UTC (permalink / raw) To: Zhang, Xiong Y, Xen-devel On 29/01/18 06:28, Zhang, Xiong Y wrote: > Today I found xen 4.10 (or staging branch) with dom0 4.15 kernel, dom0 > couldn’t boot up and it print the following error, is it a known issue ? Please post more information. Please add the following to the hypervisor boot parameters: loglvl=all guest_loglvl=all And the dom0 boot parameters should have: earlyprintk=xen Then please send the complete boot log. Probably it will be necessary to have the kernel addresses of the guest stack trace translated to symbol+offset to know what really happened. Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-01-29 5:45 ` Juergen Gross @ 2018-01-30 0:33 ` Zhang, Xiong Y 2018-01-30 10:01 ` Juergen Gross 0 siblings, 1 reply; 8+ messages in thread From: Zhang, Xiong Y @ 2018-01-30 0:33 UTC (permalink / raw) To: Juergen Gross, Xen-devel; +Cc: Zhang, Xiong Y The message is really short. Dom0 error happens before the first kernel message: ▒ Xen 4.11-unstable (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609) debug=n Tue Jan 30 02:38:14 CST 2018 (XEN) Latest ChangeSet: Wed Jan 24 12:01:55 2018 +0000 git:1252e28 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.8 (XEN) Command line: placeholder loglvl=all guest_loglvl=all com1=115200,8n1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009c800 (usable) (XEN) 000000000009c800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000c9802000 (usable) (XEN) 00000000c9802000 - 00000000c9803000 (ACPI NVS) (XEN) 00000000c9803000 - 00000000c982d000 (reserved) (XEN) 00000000c982d000 - 00000000c9881000 (usable) (XEN) 00000000c9881000 - 00000000ca082000 (reserved) (XEN) 00000000ca082000 - 00000000d71d6000 (usable) (XEN) 00000000d71d6000 - 00000000d73fc000 (reserved) (XEN) 00000000d73fc000 - 00000000d744a000 (ACPI data) (XEN) 00000000d744a000 - 00000000d7abf000 (ACPI NVS) (XEN) 00000000d7abf000 - 00000000d7fff000 (reserved) (XEN) 00000000d7fff000 - 00000000d8000000 (usable) (XEN) 00000000d8000000 - 00000000d8100000 (reserved) (XEN) 00000000f8000000 - 00000000fc000000 (reserved) (XEN) 00000000fe000000 - 00000000fe011000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000422000000 (usable) (XEN) New Xen image base address: 0xd6a00000 (XEN) ACPI: RSDP 000F05B0, 0024 (r2 DELL ) (XEN) ACPI: XSDT D741C0A0, 00C4 (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FACP D743E770, 010C (r5 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: DSDT D741C1F8, 22574 (r2 DELL CBX3 1072009 INTL 20120913) (XEN) ACPI: FACS D7ABEF80, 0040 (XEN) ACPI: APIC D743E880, 0084 (r3 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FPDT D743E908, 0044 (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FIDT D743E950, 009C (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: MCFG D743E9F0, 003C (r1 DELL CBX3 1072009 MSFT 97) (XEN) ACPI: HPET D743EA30, 0038 (r1 DELL CBX3 1072009 AMI. 5000B) (XEN) ACPI: SSDT D743EA68, 036D (r1 SataRe SataTabl 1000 INTL 20120913) (XEN) ACPI: SSDT D743EDD8, 53B2 (r2 SaSsdt SaSsdt 3000 INTL 20120913) (XEN) ACPI: UEFI D7444190, 0042 (r1 0 0) (XEN) ACPI: LPIT D74441D8, 0094 (r1 INTEL SKL 0 MSFT 5F) (XEN) ACPI: SSDT D7444270, 0248 (r2 INTEL sensrhub 0 INTL 20120913) (XEN) ACPI: SSDT D74444B8, 2BAE (r2 INTEL PtidDevc 1000 INTL 20120913) (XEN) ACPI: SSDT D7447068, 0BE3 (r2 INTEL Ther_Rvp 1000 INTL 20120913) (XEN) ACPI: DBGP D7447C50, 0034 (r1 INTEL 0 MSFT 5F) (XEN) ACPI: DBG2 D7447C88, 0054 (r0 INTEL 0 MSFT 5F) (XEN) ACPI: SSDT D7447CE0, 0613 (r2 INTEL DELL__MT 0 INTL 20120913) (XEN) ACPI: SSDT D74482F8, 0E73 (r2 CpuRef CpuSsdt 3000 INTL 20120913) (XEN) ACPI: SLIC D7449170, 0176 (r3 DELL CBX3 1072009 MSFT 10013) (XEN) ACPI: DMAR D74492E8, 00A8 (r1 INTEL SKL 1 INTL 1) (XEN) ACPI: ASF! D7449390, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) System RAM: 16265MB (16655644kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000422000000 (XEN) Domain heap initialised (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 94 (0x5e), Stepping 3 (raw 000506e3) (XEN) found SMP MP-table at 000fcdd0 (XEN) DMI 2.8 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x1808 (32 bits) (XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800] (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - d7abef80/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[d7abef8c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) [VT-D] RMRR address range d9800000..dbffffff not in reserved memory; need "iommu_inclusive_mapping=1"? (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X (XEN) Not enabling x2APIC (upon firmware request) (XEN) xstate: size: 0x440 and states: 0x1f (XEN) CPU0: Intel machine check reporting enabled (XEN) Speculative mitigation facilities: (XEN) BTI mitigations: Thunk N/A (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 23.999MHz HPET (XEN) Detected 3192.041 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d08041b7f8 -> ffff82d08041cef0 (XEN) spurious 8259A interrupt: IRQ7. (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at f8000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) nr_sockets: 1 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 (XEN) TSC deadline timer enabled (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: MWAIT substates: 0x142120 (XEN) mwait-idle: v0.4.1 model 0x5e (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - VMCS shadowing (XEN) - VM Functions (XEN) - Virtualisation Exceptions (XEN) - Page Modification Logging (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) [VT-D]INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = ffff82c00021d000 (XEN) [VT-D]INTR-REMAP: reason 22 - Present field in the IRTE entry is clear (XEN) Brought up 4 CPUs (XEN) build-id: 1af11d266142abd767fc35f7e50dcc71428a6ff2 (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 696 PIRQs (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2b65000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000040c000000->0000000410000000 (4046102 pages to be allocated) (XEN) Init. ramdisk: 000000041f030000->0000000421ffff90 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff82b65000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: 0000008000000000->0000008001f16730 (XEN) Start info: ffffffff82b65000->ffffffff82b654b4 (XEN) Xenstore ring: 0000000000000000->0000000000000000 (XEN) Console ring: 0000000000000000->0000000000000000 (XEN) Page tables: ffffffff82b66000->ffffffff82b7f000 (XEN) Boot stack: ffffffff82b7f000->ffffffff82b80000 (XEN) TOTAL: ffffffff80000000->ffffffff82c00000 (XEN) ENTRY ADDRESS: ffffffff826a3180 (XEN) Dom0 has maximum 4 VCPUs (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ..................................done. (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 460kB init memory (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] (XEN) Pagetable walk from 0000000000000028: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d0803530e4 x86_64/entry.S#create_bounce_frame+0x135/0x151 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.11-unstable x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff8103f78b>] (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) (XEN) rax: 0000000000000000 rbx: ffffffff81e06020 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: ffffffff82403e90 rdi: ffffffff82403e8c (XEN) rbp: ffffffff82403ec8 rsp: ffffffff82403e10 r8: ffffffff82403f00 (XEN) r9: 00000000ffffffff r10: ffffffff82403f04 r11: 0000000000000000 (XEN) r12: ffffffff82403e88 r13: ffffffff82403e78 r14: ffffffff82403e80 (XEN) r15: ffffffff82403e84 cr0: 000000008005003b cr4: 00000000003526e0 (XEN) cr3: 000000040eb66000 cr2: 0000000000000028 (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff82403e10: (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103f78b (XEN) 000000010000e030 0000000000010092 ffffffff82403e58 000000000000e02b (XEN) 0000000000000000 ffffffff826591e0 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff826591e0 ffffffff82403f04 (XEN) ffffffff82403f00 ffffffff82403efc ffffffff82403ef8 ffffffff82403f40 (XEN) ffffffff81040343 ffffffff82403f14 ffffffff82403f10 ffffffff82403f0c (XEN) ffffffff82403f08 0000000000003027 0000000000000000 0000000080000008 (XEN) 0000000000000000 ffffffff81032100 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff82403ff8 ffffffff826ac35d (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) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. (XEN) APIC error on CPU0: 40(00) (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. thanks > -----Original Message----- > From: Juergen Gross [mailto:jgross@suse.com] > Sent: Monday, January 29, 2018 1:45 PM > To: Zhang, Xiong Y <xiong.y.zhang@intel.com>; Xen-devel > <xen-devel@lists.xen.org> > Subject: Re: [Xen-devel] [bug]xen 4.10 + dom0 4.15 couldn't boot up > > On 29/01/18 06:28, Zhang, Xiong Y wrote: > > Today I found xen 4.10 (or staging branch) with dom0 4.15 kernel, dom0 > > couldn't boot up and it print the following error, is it a known issue ? > > Please post more information. Please add the following to the hypervisor > boot parameters: > > loglvl=all guest_loglvl=all > > And the dom0 boot parameters should have: > > earlyprintk=xen > > Then please send the complete boot log. Probably it will be necessary to have > the kernel addresses of the guest stack trace translated to > symbol+offset to know what really happened. > > > Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-01-30 0:33 ` Zhang, Xiong Y @ 2018-01-30 10:01 ` Juergen Gross 2018-02-01 6:20 ` Zhang, Xiong Y 0 siblings, 1 reply; 8+ messages in thread From: Juergen Gross @ 2018-01-30 10:01 UTC (permalink / raw) To: Zhang, Xiong Y, Xen-devel On 30/01/18 01:33, Zhang, Xiong Y wrote: > The message is really short. Dom0 error happens before the first kernel message: > > ▒ Xen 4.11-unstable > (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609) debug=n Tue Jan 30 02:38:14 CST 2018 Aah, just saw that now: can you please use a hypervisor with debug=y? This should add some more messages to the log which might give some more insight. ... > (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] > (XEN) Pagetable walk from 0000000000000028: > (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff > (XEN) domain_crash_sync called from entry.S: fault at ffff82d0803530e4 x86_64/entry.S#create_bounce_frame+0x135/0x151 > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-4.11-unstable x86_64 debug=n Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: e033:[<ffffffff8103f78b>] > (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) > (XEN) rax: 0000000000000000 rbx: ffffffff81e06020 rcx: 0000000000000000 > (XEN) rdx: 0000000000000000 rsi: ffffffff82403e90 rdi: ffffffff82403e8c > (XEN) rbp: ffffffff82403ec8 rsp: ffffffff82403e10 r8: ffffffff82403f00 > (XEN) r9: 00000000ffffffff r10: ffffffff82403f04 r11: 0000000000000000 > (XEN) r12: ffffffff82403e88 r13: ffffffff82403e78 r14: ffffffff82403e80 > (XEN) r15: ffffffff82403e84 cr0: 000000008005003b cr4: 00000000003526e0 > (XEN) cr3: 000000040eb66000 cr2: 0000000000000028 > (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff82403e10: > (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103f78b > (XEN) 000000010000e030 0000000000010092 ffffffff82403e58 000000000000e02b > (XEN) 0000000000000000 ffffffff826591e0 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff826591e0 ffffffff82403f04 > (XEN) ffffffff82403f00 ffffffff82403efc ffffffff82403ef8 ffffffff82403f40 > (XEN) ffffffff81040343 ffffffff82403f14 ffffffff82403f10 ffffffff82403f0c > (XEN) ffffffff82403f08 0000000000003027 0000000000000000 0000000080000008 > (XEN) 0000000000000000 ffffffff81032100 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff82403ff8 ffffffff826ac35d Can you please translate the kernel addresses in this stack dump to symbol+offset (via disassembly of the kernel) or file+line (via addr2line utility)? Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-01-30 10:01 ` Juergen Gross @ 2018-02-01 6:20 ` Zhang, Xiong Y 2018-02-01 7:29 ` Juergen Gross 0 siblings, 1 reply; 8+ messages in thread From: Zhang, Xiong Y @ 2018-02-01 6:20 UTC (permalink / raw) To: Juergen Gross, Xen-devel; +Cc: Zhang, Xiong Y This is the message with debug=y Xen 4.11-unstable (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609) debug=y Tue Jan 30 02:38:14 CST 2018 (XEN) Latest ChangeSet: Wed Jan 24 12:01:55 2018 +0000 git:1252e28 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.8 (XEN) Command line: placeholder loglvl=all guest_loglvl=all com1=115200,8n1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009c800 (usable) (XEN) 000000000009c800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000c9802000 (usable) (XEN) 00000000c9802000 - 00000000c9803000 (ACPI NVS) (XEN) 00000000c9803000 - 00000000c982d000 (reserved) (XEN) 00000000c982d000 - 00000000c9881000 (usable) (XEN) 00000000c9881000 - 00000000ca082000 (reserved) (XEN) 00000000ca082000 - 00000000d71d6000 (usable) (XEN) 00000000d71d6000 - 00000000d73fc000 (reserved) (XEN) 00000000d73fc000 - 00000000d744a000 (ACPI data) (XEN) 00000000d744a000 - 00000000d7abf000 (ACPI NVS) (XEN) 00000000d7abf000 - 00000000d7fff000 (reserved) (XEN) 00000000d7fff000 - 00000000d8000000 (usable) (XEN) 00000000d8000000 - 00000000d8100000 (reserved) (XEN) 00000000f8000000 - 00000000fc000000 (reserved) (XEN) 00000000fe000000 - 00000000fe011000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000422000000 (usable) (XEN) New Xen image base address: 0xd6a00000 (XEN) ACPI: RSDP 000F05B0, 0024 (r2 DELL ) (XEN) ACPI: XSDT D741C0A0, 00C4 (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FACP D743E770, 010C (r5 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: DSDT D741C1F8, 22574 (r2 DELL CBX3 1072009 INTL 20120913) (XEN) ACPI: FACS D7ABEF80, 0040 (XEN) ACPI: APIC D743E880, 0084 (r3 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FPDT D743E908, 0044 (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: FIDT D743E950, 009C (r1 DELL CBX3 1072009 AMI 10013) (XEN) ACPI: MCFG D743E9F0, 003C (r1 DELL CBX3 1072009 MSFT 97) (XEN) ACPI: HPET D743EA30, 0038 (r1 DELL CBX3 1072009 AMI. 5000B) (XEN) ACPI: SSDT D743EA68, 036D (r1 SataRe SataTabl 1000 INTL 20120913) (XEN) ACPI: SSDT D743EDD8, 53B2 (r2 SaSsdt SaSsdt 3000 INTL 20120913) (XEN) ACPI: UEFI D7444190, 0042 (r1 0 0) (XEN) ACPI: LPIT D74441D8, 0094 (r1 INTEL SKL 0 MSFT 5F) (XEN) ACPI: SSDT D7444270, 0248 (r2 INTEL sensrhub 0 INTL 20120913) (XEN) ACPI: SSDT D74444B8, 2BAE (r2 INTEL PtidDevc 1000 INTL 20120913) (XEN) ACPI: SSDT D7447068, 0BE3 (r2 INTEL Ther_Rvp 1000 INTL 20120913) (XEN) ACPI: DBGP D7447C50, 0034 (r1 INTEL 0 MSFT 5F) (XEN) ACPI: DBG2 D7447C88, 0054 (r0 INTEL 0 MSFT 5F) (XEN) ACPI: SSDT D7447CE0, 0613 (r2 INTEL DELL__MT 0 INTL 20120913) (XEN) ACPI: SSDT D74482F8, 0E73 (r2 CpuRef CpuSsdt 3000 INTL 20120913) (XEN) ACPI: SLIC D7449170, 0176 (r3 DELL CBX3 1072009 MSFT 10013) (XEN) ACPI: DMAR D74492E8, 00A8 (r1 INTEL SKL 1 INTL 1) (XEN) ACPI: ASF! D7449390, 00A5 (r32 INTEL HCG 1 TFSM F4240) (XEN) System RAM: 16265MB (16655644kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000422000000 (XEN) Domain heap initialised (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 94 (0x5e), Stepping 3 (raw 000506e3) (XEN) found SMP MP-table at 000fcdd0 (XEN) DMI 2.8 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x1808 (32 bits) (XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800] (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - d7abef80/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[d7abef8c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) [VT-D] RMRR address range d9800000..dbffffff not in reserved memory; need "iommu_inclusive_mapping=1"? (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X (XEN) Not enabling x2APIC (upon firmware request) (XEN) xstate: size: 0x440 and states: 0x1f (XEN) mce_intel.c:782: MCA Capability: firstbank 0, extended MCE MSR 0, BCAST, CMCI (XEN) CPU0: Intel machine check reporting enabled (XEN) Speculative mitigation facilities: (XEN) BTI mitigations: Thunk N/A (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 23.999MHz HPET (XEN) Detected 3192.057 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d08044c7f8 -> ffff82d08044de30 (XEN) spurious 8259A interrupt: IRQ7. (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at f8000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) nr_sockets: 1 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 (XEN) TSC deadline timer enabled (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: MWAIT substates: 0x142120 (XEN) mwait-idle: v0.4.1 model 0x5e (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) - VMCS shadowing (XEN) - VM Functions (XEN) - Virtualisation Exceptions (XEN) - Page Modification Logging (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) [VT-D]INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = ffff82c00021d000 (XEN) [VT-D]INTR-REMAP: reason 25 - Blocked a compatibility format interrupt request (XEN) Brought up 4 CPUs (XEN) build-id: 97842bcc5c98cc448bfc0221873efaf29d1065b6 (XEN) Running stub recovery selftests... (XEN) traps.c:1550: GPF (0000): ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d080367cb2 (XEN) traps.c:735: Trap 12: ffff82d0bffff040 [ffff82d0bffff040] -> ffff82d080367cb2 (XEN) traps.c:1077: Trap 3: ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d080367cb2 (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 696 PIRQs (XEN) grant_table.c:1680:IDLEv0 Expanding d0 grant table from 0 to 1 frames (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) ELF: phdr: paddr=0x1000000 memsz=0x11e5000 (XEN) ELF: phdr: paddr=0x2200000 memsz=0x5ee000 (XEN) ELF: phdr: paddr=0x27ee000 memsz=0x23a98 (XEN) ELF: phdr: paddr=0x2812000 memsz=0x4b2000 (XEN) ELF: memory: 0x1000000 -> 0x2cc4000 (XEN) ELF: note: GUEST_OS = "linux" (XEN) ELF: note: GUEST_VERSION = "2.6" (XEN) ELF: note: XEN_VERSION = "xen-3.0" (XEN) ELF: note: VIRT_BASE = 0xffffffff80000000 (XEN) ELF: note: INIT_P2M = 0x8000000000 (XEN) ELF: note: ENTRY = 0xffffffff82812180 (XEN) ELF: note: HYPERCALL_PAGE = 0xffffffff81001000 (XEN) ELF: note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" (XEN) ELF: note: SUPPORTED_FEATURES = 0x801 (XEN) ELF: note: PAE_MODE = "yes" (XEN) ELF: note: LOADER = "generic" (XEN) ELF: note: unknown (0xd) (XEN) ELF: note: SUSPEND_CANCEL = 0x1 (XEN) ELF: note: MOD_START_PFN = 0x1 (XEN) ELF: note: HV_START_LOW = 0xffff800000000000 (XEN) ELF: note: PADDR_OFFSET = 0 (XEN) ELF: note: PHYS32_ENTRY = 0x1000360 (XEN) ELF: Found PVH image (XEN) ELF: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff82cc4000 (XEN) virt_entry = 0xffffffff82812180 (XEN) p2m_base = 0x8000000000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2cc4000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00000003f8000000->00000003fc000000 (3967420 pages to be allocated) (XEN) Init. ramdisk: 000000040bd0e000->0000000421fff4a6 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff82cc4000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: 0000008000000000->0000008001f16570 (XEN) Start info: ffffffff82cc4000->ffffffff82cc44b4 (XEN) Xenstore ring: 0000000000000000->0000000000000000 (XEN) Console ring: 0000000000000000->0000000000000000 (XEN) Page tables: ffffffff82cc5000->ffffffff82ce0000 (XEN) Boot stack: ffffffff82ce0000->ffffffff82ce1000 (XEN) TOTAL: ffffffff80000000->ffffffff83000000 (XEN) ENTRY ADDRESS: ffffffff82812180 (XEN) Dom0 has maximum 4 VCPUs (XEN) ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff821e5000 (XEN) ELF: phdr 1 at 0xffffffff82200000 -> 0xffffffff827ee000 (XEN) ELF: phdr 2 at 0xffffffff827ee000 -> 0xffffffff82811a98 (XEN) ELF: phdr 3 at 0xffffffff82812000 -> 0xffffffff82a42000 (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ..................................done. (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 452kB init memory (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] (XEN) Pagetable walk from 0000000000000028: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d080364e58 x86_64/entry.S#create_bounce_frame+0x143/0x15b (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.11-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff8103ca29>] (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) (XEN) rax: 0000000000000000 rbx: ffffffff81e05fe0 rcx: 0000000000000000 (XEN) rdx: 0000000000000030 rsi: ffffffff82203f04 rdi: ffffffff82451f60 (XEN) rbp: ffffffff82203f08 rsp: ffffffff82203e20 r8: ffffffff82203f08 (XEN) r9: 00000000ffffffff r10: ffffffff82203f0c r11: 0000000000000000 (XEN) r12: ffffffff82203f0c r13: ffffffff82203e88 r14: ffffffff82203f00 (XEN) r15: ffffffff82203e98 cr0: 000000008005003b cr4: 00000000003526e0 (XEN) cr3: 00000003facc5000 cr2: 0000000000000028 (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff82203e20: (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103ca29 (XEN) 000000010000e030 0000000000010092 ffffffff82203e68 000000000000e02b (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) ffffffff82451f60 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff82451f60 ffffffff82203f08 (XEN) ffffffff82203f0c ffffffff82203f04 ffffffff82203f00 ffffffff82203f1c (XEN) ffffffff8103d611 ffffffff82203f10 ffffffff82203f14 ffffffff82203f18 (XEN) 0000000000003027 0000000000000000 0000000080000008 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff8281ba11 0000000000000000 (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) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. (XEN) APIC error on CPU0: 40(00) (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. addr2line -f -e vmlinux ffffffff8103ca29 init_scattered_cpuid_features arch/x86/kernel/cpu/scattered.c:38 addr2line -f -e vmlinux ffffffff8103d611 get_cpu_cap arch/x86/kernel/cpu/common.c:843 addr2line -f -e vmlinux ffffffff8281ba11 xen_start_kernel arch/x86/xen/enlighten_pv.c:1264 All the other ffffffffxxxxxxxx are data address, not code address. thanks > -----Original Message----- > From: Juergen Gross [mailto:jgross@suse.com] > Sent: Tuesday, January 30, 2018 6:01 PM > To: Zhang, Xiong Y <xiong.y.zhang@intel.com>; Xen-devel > <xen-devel@lists.xen.org> > Subject: Re: [Xen-devel] [bug]xen 4.10 + dom0 4.15 couldn't boot up > > On 30/01/18 01:33, Zhang, Xiong Y wrote: > > The message is really short. Dom0 error happens before the first kernel > message: > > > > ▒ Xen 4.11-unstable > > (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu > > 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609) debug=n Tue Jan 30 02:38:14 > > CST 2018 > > Aah, just saw that now: can you please use a hypervisor with debug=y? > This should add some more messages to the log which might give some more > insight. > > ... > > > (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] > > (XEN) Pagetable walk from 0000000000000028: > > (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff > > (XEN) domain_crash_sync called from entry.S: fault at ffff82d0803530e4 > > x86_64/entry.S#create_bounce_frame+0x135/0x151 > > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > > (XEN) ----[ Xen-4.11-unstable x86_64 debug=n Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) RIP: e033:[<ffffffff8103f78b>] > > (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) > > (XEN) rax: 0000000000000000 rbx: ffffffff81e06020 rcx: > 0000000000000000 > > (XEN) rdx: 0000000000000000 rsi: ffffffff82403e90 rdi: > ffffffff82403e8c > > (XEN) rbp: ffffffff82403ec8 rsp: ffffffff82403e10 r8: ffffffff82403f00 > > (XEN) r9: 00000000ffffffff r10: ffffffff82403f04 r11: > 0000000000000000 > > (XEN) r12: ffffffff82403e88 r13: ffffffff82403e78 r14: ffffffff82403e80 > > (XEN) r15: ffffffff82403e84 cr0: 000000008005003b cr4: > 00000000003526e0 > > (XEN) cr3: 000000040eb66000 cr2: 0000000000000028 > > (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: > 0000000000000000 > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > > (XEN) Guest stack trace from rsp=ffffffff82403e10: > > (XEN) 0000000000000000 0000000000000000 0000000000000000 > ffffffff8103f78b > > (XEN) 000000010000e030 0000000000010092 ffffffff82403e58 > 000000000000e02b > > (XEN) 0000000000000000 ffffffff826591e0 0000000000000000 > 0000000000000000 > > (XEN) 0000000000000000 0000000000000000 0000000000000000 > 0000000000000000 > > (XEN) 0000000000000000 0000000000000000 ffffffff826591e0 > ffffffff82403f04 > > (XEN) ffffffff82403f00 ffffffff82403efc ffffffff82403ef8 ffffffff82403f40 > > (XEN) ffffffff81040343 ffffffff82403f14 ffffffff82403f10 ffffffff82403f0c > > (XEN) ffffffff82403f08 0000000000003027 0000000000000000 > 0000000080000008 > > (XEN) 0000000000000000 ffffffff81032100 0000000000000000 > 0000000000000000 > > (XEN) 0000000000000000 0000000000000000 ffffffff82403ff8 > ffffffff826ac35d > > Can you please translate the kernel addresses in this stack dump to > symbol+offset (via disassembly of the kernel) or file+line (via > addr2line utility)? > > Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-02-01 6:20 ` Zhang, Xiong Y @ 2018-02-01 7:29 ` Juergen Gross 2018-02-01 9:14 ` Jan Beulich [not found] ` <5A72E89002000078001A43DB@suse.com> 0 siblings, 2 replies; 8+ messages in thread From: Juergen Gross @ 2018-02-01 7:29 UTC (permalink / raw) To: Zhang, Xiong Y, Xen-devel On 01/02/18 07:20, Zhang, Xiong Y wrote: > This is the message with debug=y > Xen 4.11-unstable > (XEN) Xen version 4.11-unstable (test@) (gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609) debug=y Tue Jan 30 02:38:14 CST 2018 > (XEN) Latest ChangeSet: Wed Jan 24 12:01:55 2018 +0000 git:1252e28 > (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.8 > (XEN) Command line: placeholder loglvl=all guest_loglvl=all com1=115200,8n1 console=com1,vga > (XEN) Xen image load base address: 0 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009c800 (usable) > (XEN) 000000000009c800 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000c9802000 (usable) > (XEN) 00000000c9802000 - 00000000c9803000 (ACPI NVS) > (XEN) 00000000c9803000 - 00000000c982d000 (reserved) > (XEN) 00000000c982d000 - 00000000c9881000 (usable) > (XEN) 00000000c9881000 - 00000000ca082000 (reserved) > (XEN) 00000000ca082000 - 00000000d71d6000 (usable) > (XEN) 00000000d71d6000 - 00000000d73fc000 (reserved) > (XEN) 00000000d73fc000 - 00000000d744a000 (ACPI data) > (XEN) 00000000d744a000 - 00000000d7abf000 (ACPI NVS) > (XEN) 00000000d7abf000 - 00000000d7fff000 (reserved) > (XEN) 00000000d7fff000 - 00000000d8000000 (usable) > (XEN) 00000000d8000000 - 00000000d8100000 (reserved) > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > (XEN) 00000000fe000000 - 00000000fe011000 (reserved) > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000422000000 (usable) > (XEN) New Xen image base address: 0xd6a00000 > (XEN) ACPI: RSDP 000F05B0, 0024 (r2 DELL ) > (XEN) ACPI: XSDT D741C0A0, 00C4 (r1 DELL CBX3 1072009 AMI 10013) > (XEN) ACPI: FACP D743E770, 010C (r5 DELL CBX3 1072009 AMI 10013) > (XEN) ACPI: DSDT D741C1F8, 22574 (r2 DELL CBX3 1072009 INTL 20120913) > (XEN) ACPI: FACS D7ABEF80, 0040 > (XEN) ACPI: APIC D743E880, 0084 (r3 DELL CBX3 1072009 AMI 10013) > (XEN) ACPI: FPDT D743E908, 0044 (r1 DELL CBX3 1072009 AMI 10013) > (XEN) ACPI: FIDT D743E950, 009C (r1 DELL CBX3 1072009 AMI 10013) > (XEN) ACPI: MCFG D743E9F0, 003C (r1 DELL CBX3 1072009 MSFT 97) > (XEN) ACPI: HPET D743EA30, 0038 (r1 DELL CBX3 1072009 AMI. 5000B) > (XEN) ACPI: SSDT D743EA68, 036D (r1 SataRe SataTabl 1000 INTL 20120913) > (XEN) ACPI: SSDT D743EDD8, 53B2 (r2 SaSsdt SaSsdt 3000 INTL 20120913) > (XEN) ACPI: UEFI D7444190, 0042 (r1 0 0) > (XEN) ACPI: LPIT D74441D8, 0094 (r1 INTEL SKL 0 MSFT 5F) > (XEN) ACPI: SSDT D7444270, 0248 (r2 INTEL sensrhub 0 INTL 20120913) > (XEN) ACPI: SSDT D74444B8, 2BAE (r2 INTEL PtidDevc 1000 INTL 20120913) > (XEN) ACPI: SSDT D7447068, 0BE3 (r2 INTEL Ther_Rvp 1000 INTL 20120913) > (XEN) ACPI: DBGP D7447C50, 0034 (r1 INTEL 0 MSFT 5F) > (XEN) ACPI: DBG2 D7447C88, 0054 (r0 INTEL 0 MSFT 5F) > (XEN) ACPI: SSDT D7447CE0, 0613 (r2 INTEL DELL__MT 0 INTL 20120913) > (XEN) ACPI: SSDT D74482F8, 0E73 (r2 CpuRef CpuSsdt 3000 INTL 20120913) > (XEN) ACPI: SLIC D7449170, 0176 (r3 DELL CBX3 1072009 MSFT 10013) > (XEN) ACPI: DMAR D74492E8, 00A8 (r1 INTEL SKL 1 INTL 1) > (XEN) ACPI: ASF! D7449390, 00A5 (r32 INTEL HCG 1 TFSM F4240) > (XEN) System RAM: 16265MB (16655644kB) > (XEN) No NUMA configuration found > (XEN) Faking a node at 0000000000000000-0000000422000000 > (XEN) Domain heap initialised > (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 94 (0x5e), Stepping 3 (raw 000506e3) > (XEN) found SMP MP-table at 000fcdd0 > (XEN) DMI 2.8 present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0x1808 (32 bits) > (XEN) ACPI: v5 SLEEP INFO: control[1:1804], status[1:1800] > (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3 > (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:1804,1:0], pm1x_evt[1:1800,1:0] > (XEN) ACPI: 32/64X FACS address mismatch in FADT - d7abef80/0000000000000000, using 32 > (XEN) ACPI: wakeup_vec[d7abef8c], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) > (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) > (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) > (XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) ACPI: IRQ9 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 > (XEN) [VT-D] RMRR address range d9800000..dbffffff not in reserved memory; need "iommu_inclusive_mapping=1"? > (XEN) ERST table was not found > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) > (XEN) IRQ limits: 120 GSI, 840 MSI/MSI-X > (XEN) Not enabling x2APIC (upon firmware request) > (XEN) xstate: size: 0x440 and states: 0x1f > (XEN) mce_intel.c:782: MCA Capability: firstbank 0, extended MCE MSR 0, BCAST, CMCI > (XEN) CPU0: Intel machine check reporting enabled > (XEN) Speculative mitigation facilities: > (XEN) BTI mitigations: Thunk N/A > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Platform timer is 23.999MHz HPET > (XEN) Detected 3192.057 MHz processor. > (XEN) Initing memory sharing. > (XEN) alt table ffff82d08044c7f8 -> ffff82d08044de30 > (XEN) spurious 8259A interrupt: IRQ7. > (XEN) PCI: MCFG configuration 0: base f8000000 segment 0000 buses 00 - 3f > (XEN) PCI: MCFG area at f8000000 reserved in E820 > (XEN) PCI: Using MCFG for segment 0000 bus 00-3f > (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. > (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Posted Interrupt not enabled. > (XEN) Intel VT-d Shared EPT tables enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Interrupt remapping enabled > (XEN) nr_sockets: 1 > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 > (XEN) TSC deadline timer enabled > (XEN) Allocated console ring of 32 KiB. > (XEN) mwait-idle: MWAIT substates: 0x142120 > (XEN) mwait-idle: v0.4.1 model 0x5e > (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) - VMCS shadowing > (XEN) - VM Functions > (XEN) - Virtualisation Exceptions > (XEN) - Page Modification Logging > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > (XEN) [VT-D]INTR-REMAP: Request device [0000:f0:1f.0] fault index 0, iommu reg = ffff82c00021d000 > (XEN) [VT-D]INTR-REMAP: reason 25 - Blocked a compatibility format interrupt request > (XEN) Brought up 4 CPUs > (XEN) build-id: 97842bcc5c98cc448bfc0221873efaf29d1065b6 > (XEN) Running stub recovery selftests... > (XEN) traps.c:1550: GPF (0000): ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d080367cb2 > (XEN) traps.c:735: Trap 12: ffff82d0bffff040 [ffff82d0bffff040] -> ffff82d080367cb2 > (XEN) traps.c:1077: Trap 3: ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d080367cb2 > (XEN) ACPI sleep modes: S3 > (XEN) VPMU: disabled > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) Dom0 has maximum 696 PIRQs > (XEN) grant_table.c:1680:IDLEv0 Expanding d0 grant table from 0 to 1 frames > (XEN) NX (Execute Disable) protection active > (XEN) *** LOADING DOMAIN 0 *** > (XEN) ELF: phdr: paddr=0x1000000 memsz=0x11e5000 > (XEN) ELF: phdr: paddr=0x2200000 memsz=0x5ee000 > (XEN) ELF: phdr: paddr=0x27ee000 memsz=0x23a98 > (XEN) ELF: phdr: paddr=0x2812000 memsz=0x4b2000 > (XEN) ELF: memory: 0x1000000 -> 0x2cc4000 > (XEN) ELF: note: GUEST_OS = "linux" > (XEN) ELF: note: GUEST_VERSION = "2.6" > (XEN) ELF: note: XEN_VERSION = "xen-3.0" > (XEN) ELF: note: VIRT_BASE = 0xffffffff80000000 > (XEN) ELF: note: INIT_P2M = 0x8000000000 > (XEN) ELF: note: ENTRY = 0xffffffff82812180 > (XEN) ELF: note: HYPERCALL_PAGE = 0xffffffff81001000 > (XEN) ELF: note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" > (XEN) ELF: note: SUPPORTED_FEATURES = 0x801 > (XEN) ELF: note: PAE_MODE = "yes" > (XEN) ELF: note: LOADER = "generic" > (XEN) ELF: note: unknown (0xd) > (XEN) ELF: note: SUSPEND_CANCEL = 0x1 > (XEN) ELF: note: MOD_START_PFN = 0x1 > (XEN) ELF: note: HV_START_LOW = 0xffff800000000000 > (XEN) ELF: note: PADDR_OFFSET = 0 > (XEN) ELF: note: PHYS32_ENTRY = 0x1000360 > (XEN) ELF: Found PVH image > (XEN) ELF: addresses: > (XEN) virt_base = 0xffffffff80000000 > (XEN) elf_paddr_offset = 0x0 > (XEN) virt_offset = 0xffffffff80000000 > (XEN) virt_kstart = 0xffffffff81000000 > (XEN) virt_kend = 0xffffffff82cc4000 > (XEN) virt_entry = 0xffffffff82812180 > (XEN) p2m_base = 0x8000000000 > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2cc4000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 00000003f8000000->00000003fc000000 (3967420 pages to be allocated) > (XEN) Init. ramdisk: 000000040bd0e000->0000000421fff4a6 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff82cc4000 > (XEN) Init. ramdisk: 0000000000000000->0000000000000000 > (XEN) Phys-Mach map: 0000008000000000->0000008001f16570 > (XEN) Start info: ffffffff82cc4000->ffffffff82cc44b4 > (XEN) Xenstore ring: 0000000000000000->0000000000000000 > (XEN) Console ring: 0000000000000000->0000000000000000 > (XEN) Page tables: ffffffff82cc5000->ffffffff82ce0000 > (XEN) Boot stack: ffffffff82ce0000->ffffffff82ce1000 > (XEN) TOTAL: ffffffff80000000->ffffffff83000000 > (XEN) ENTRY ADDRESS: ffffffff82812180 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff821e5000 > (XEN) ELF: phdr 1 at 0xffffffff82200000 -> 0xffffffff827ee000 > (XEN) ELF: phdr 2 at 0xffffffff827ee000 -> 0xffffffff82811a98 > (XEN) ELF: phdr 3 at 0xffffffff82812000 -> 0xffffffff82a42000 > (XEN) Bogus DMIBAR 0xfed18001 on 0000:00:00.0 > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs > (XEN) ..................................done. > (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 452kB init memory > (XEN) d0v0 Unhandled page fault fault/trap [#14, ec=0000] > (XEN) Pagetable walk from 0000000000000028: > (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff > (XEN) domain_crash_sync called from entry.S: fault at ffff82d080364e58 x86_64/entry.S#create_bounce_frame+0x143/0x15b > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-4.11-unstable x86_64 debug=y Not tainted ]---- > (XEN) CPU: 0 > (XEN) RIP: e033:[<ffffffff8103ca29>] > (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) > (XEN) rax: 0000000000000000 rbx: ffffffff81e05fe0 rcx: 0000000000000000 > (XEN) rdx: 0000000000000030 rsi: ffffffff82203f04 rdi: ffffffff82451f60 > (XEN) rbp: ffffffff82203f08 rsp: ffffffff82203e20 r8: ffffffff82203f08 > (XEN) r9: 00000000ffffffff r10: ffffffff82203f0c r11: 0000000000000000 > (XEN) r12: ffffffff82203f0c r13: ffffffff82203e88 r14: ffffffff82203f00 > (XEN) r15: ffffffff82203e98 cr0: 000000008005003b cr4: 00000000003526e0 > (XEN) cr3: 00000003facc5000 cr2: 0000000000000028 > (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff82203e20: > (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103ca29 > (XEN) 000000010000e030 0000000000010092 ffffffff82203e68 000000000000e02b > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) ffffffff82451f60 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff82451f60 ffffffff82203f08 > (XEN) ffffffff82203f0c ffffffff82203f04 ffffffff82203f00 ffffffff82203f1c > (XEN) ffffffff8103d611 ffffffff82203f10 ffffffff82203f14 ffffffff82203f18 > (XEN) 0000000000003027 0000000000000000 0000000080000008 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff8281ba11 0000000000000000 > (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) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > (XEN) APIC error on CPU0: 40(00) > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. > > addr2line -f -e vmlinux ffffffff8103ca29 > init_scattered_cpuid_features > arch/x86/kernel/cpu/scattered.c:38 And this is the problem: it seems as if the compiler now generates an access via %gs in this function, but this segment hasn't been setup at this stage of the boot process. I'm trying to move up initialization of the %gs segment. Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up 2018-02-01 7:29 ` Juergen Gross @ 2018-02-01 9:14 ` Jan Beulich [not found] ` <5A72E89002000078001A43DB@suse.com> 1 sibling, 0 replies; 8+ messages in thread From: Jan Beulich @ 2018-02-01 9:14 UTC (permalink / raw) To: Juergen Gross; +Cc: Xiong Y Zhang, Xen-devel >>> On 01.02.18 at 08:29, <jgross@suse.com> wrote: > On 01/02/18 07:20, Zhang, Xiong Y wrote: >> (XEN) Domain 0 (vcpu#0) crashed on cpu#0: >> (XEN) ----[ Xen-4.11-unstable x86_64 debug=y Not tainted ]---- >> (XEN) CPU: 0 >> (XEN) RIP: e033:[<ffffffff8103ca29>] >> (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) >> (XEN) rax: 0000000000000000 rbx: ffffffff81e05fe0 rcx: 0000000000000000 >> (XEN) rdx: 0000000000000030 rsi: ffffffff82203f04 rdi: ffffffff82451f60 >> (XEN) rbp: ffffffff82203f08 rsp: ffffffff82203e20 r8: ffffffff82203f08 >> (XEN) r9: 00000000ffffffff r10: ffffffff82203f0c r11: 0000000000000000 >> (XEN) r12: ffffffff82203f0c r13: ffffffff82203e88 r14: ffffffff82203f00 >> (XEN) r15: ffffffff82203e98 cr0: 000000008005003b cr4: 00000000003526e0 >> (XEN) cr3: 00000003facc5000 cr2: 0000000000000028 >> (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 >> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 >> (XEN) Guest stack trace from rsp=ffffffff82203e20: >> (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103ca29 >> (XEN) 000000010000e030 0000000000010092 ffffffff82203e68 000000000000e02b >> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 >> (XEN) ffffffff82451f60 0000000000000000 0000000000000000 0000000000000000 >> (XEN) 0000000000000000 0000000000000000 ffffffff82451f60 ffffffff82203f08 >> (XEN) ffffffff82203f0c ffffffff82203f04 ffffffff82203f00 ffffffff82203f1c >> (XEN) ffffffff8103d611 ffffffff82203f10 ffffffff82203f14 ffffffff82203f18 >> (XEN) 0000000000003027 0000000000000000 0000000080000008 0000000000000000 >> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 >> (XEN) 0000000000000000 0000000000000000 ffffffff8281ba11 0000000000000000 >> (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) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >> (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. >> (XEN) APIC error on CPU0: 40(00) >> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >> >> addr2line -f -e vmlinux ffffffff8103ca29 >> init_scattered_cpuid_features >> arch/x86/kernel/cpu/scattered.c:38 > > And this is the problem: it seems as if the compiler now generates an > access via %gs in this function, but this segment hasn't been setup at > this stage of the boot process. > > I'm trying to move up initialization of the %gs segment. This can be done _really_ early, as our old XenoLinux kernel shows (4.4 based): startup_64: movq $(init_thread_union+THREAD_SIZE-8),%rsp /* rsi is pointer to startup info structure. pass it to C */ movq %rsi,%rdi /* Set up %gs. * * The base of %gs always points to the bottom of the irqstack * union. If the stack protector canary is enabled, it is * located at %gs:40. Note that, on SMP, the boot cpu uses * init data section till per cpu areas are set up. */ movl $MSR_GS_BASE,%ecx movq $INIT_PER_CPU_VAR(irq_stack_union),%rax cdq wrmsr I won't make any guarantees on the applicability of everything the comment says, though. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <5A72E89002000078001A43DB@suse.com>]
* Re: [bug]xen 4.10 + dom0 4.15 couldn't boot up [not found] ` <5A72E89002000078001A43DB@suse.com> @ 2018-02-01 9:22 ` Juergen Gross 0 siblings, 0 replies; 8+ messages in thread From: Juergen Gross @ 2018-02-01 9:22 UTC (permalink / raw) To: Jan Beulich; +Cc: Xiong Y Zhang, Xen-devel On 01/02/18 10:14, Jan Beulich wrote: >>>> On 01.02.18 at 08:29, <jgross@suse.com> wrote: >> On 01/02/18 07:20, Zhang, Xiong Y wrote: >>> (XEN) Domain 0 (vcpu#0) crashed on cpu#0: >>> (XEN) ----[ Xen-4.11-unstable x86_64 debug=y Not tainted ]---- >>> (XEN) CPU: 0 >>> (XEN) RIP: e033:[<ffffffff8103ca29>] >>> (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d0v0) >>> (XEN) rax: 0000000000000000 rbx: ffffffff81e05fe0 rcx: 0000000000000000 >>> (XEN) rdx: 0000000000000030 rsi: ffffffff82203f04 rdi: ffffffff82451f60 >>> (XEN) rbp: ffffffff82203f08 rsp: ffffffff82203e20 r8: ffffffff82203f08 >>> (XEN) r9: 00000000ffffffff r10: ffffffff82203f0c r11: 0000000000000000 >>> (XEN) r12: ffffffff82203f0c r13: ffffffff82203e88 r14: ffffffff82203f00 >>> (XEN) r15: ffffffff82203e98 cr0: 000000008005003b cr4: 00000000003526e0 >>> (XEN) cr3: 00000003facc5000 cr2: 0000000000000028 >>> (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 >>> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 >>> (XEN) Guest stack trace from rsp=ffffffff82203e20: >>> (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8103ca29 >>> (XEN) 000000010000e030 0000000000010092 ffffffff82203e68 000000000000e02b >>> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 >>> (XEN) ffffffff82451f60 0000000000000000 0000000000000000 0000000000000000 >>> (XEN) 0000000000000000 0000000000000000 ffffffff82451f60 ffffffff82203f08 >>> (XEN) ffffffff82203f0c ffffffff82203f04 ffffffff82203f00 ffffffff82203f1c >>> (XEN) ffffffff8103d611 ffffffff82203f10 ffffffff82203f14 ffffffff82203f18 >>> (XEN) 0000000000003027 0000000000000000 0000000080000008 0000000000000000 >>> (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 >>> (XEN) 0000000000000000 0000000000000000 ffffffff8281ba11 0000000000000000 >>> (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) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >>> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >>> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >>> (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc >>> (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. >>> (XEN) APIC error on CPU0: 40(00) >>> (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >>> >>> addr2line -f -e vmlinux ffffffff8103ca29 >>> init_scattered_cpuid_features >>> arch/x86/kernel/cpu/scattered.c:38 >> >> And this is the problem: it seems as if the compiler now generates an >> access via %gs in this function, but this segment hasn't been setup at >> this stage of the boot process. >> >> I'm trying to move up initialization of the %gs segment. > > This can be done _really_ early, as our old XenoLinux kernel shows > (4.4 based): > > startup_64: > movq $(init_thread_union+THREAD_SIZE-8),%rsp > > /* rsi is pointer to startup info structure. > pass it to C */ > movq %rsi,%rdi > > /* Set up %gs. > * > * The base of %gs always points to the bottom of the irqstack > * union. If the stack protector canary is enabled, it is > * located at %gs:40. Note that, on SMP, the boot cpu uses > * init data section till per cpu areas are set up. > */ > movl $MSR_GS_BASE,%ecx > movq $INIT_PER_CPU_VAR(irq_stack_union),%rax > cdq > wrmsr > > I won't make any guarantees on the applicability of everything the > comment says, though. Thanks for the confirmation that I'm on the right track. :-) Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2018-02-01 9:22 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-29 5:28 [bug]xen 4.10 + dom0 4.15 couldn't boot up Zhang, Xiong Y
2018-01-29 5:45 ` Juergen Gross
2018-01-30 0:33 ` Zhang, Xiong Y
2018-01-30 10:01 ` Juergen Gross
2018-02-01 6:20 ` Zhang, Xiong Y
2018-02-01 7:29 ` Juergen Gross
2018-02-01 9:14 ` Jan Beulich
[not found] ` <5A72E89002000078001A43DB@suse.com>
2018-02-01 9:22 ` Juergen Gross
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).