[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [Bug] panic on xen 4.11.2-pre
Hello,ty for the reply. I'm using the internal gfx of the Intel i3-8100. I have ECC unbuffered RAM, but I thing this shouldn't be an issue. How can I get these packages? I used the xen-hypervisor-common package from the debian buster repository. If I try to build it (debian too), I run into errors. Is there a docker build environment or something? Am 17.12.19 um 12:27 schrieb Jan Beulich: On 17.12.2019 11:02, Limitless Green wrote:Hello, I was asked via IRC to post my issue here. I got the following through the debug interface: 0x0000:0x00:0x1f.0x6: ROM: 0x10400 bytes at 0x7ffc7018 (XEN) Xen version 4.11.2-pre (Debian 4.11.1+92-g6c33308a8d-2) (pkg-xen-devel@xxxxxxxxxxxxxxxxxxxxxxx) (gcc (Debian 8.3.0-7) 8.3.0) debug=n Mon Jun 24 10:10:11 UTC 2019 (XEN) Bootloader: GRUB 2.02+dfsg1-20 (XEN) Command line: placeholder loglvl=all guest_loglvl=all com1=115200,8n1 console=com1,vga no-real-mode edd=off (XEN) Xen image load base address: 0x79e00000 (XEN) Video information: (XEN) VGA is graphics mode 1360x768, 32 bpp (XEN) Disc information: (XEN) Found 0 MBR signatures (XEN) Found 3 EDD information structures (XEN) EFI RAM map: (XEN) 0000000000000000 - 000000000009f000 (usable) (XEN) 000000000009f000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 0000000040000000 (usable) (XEN) 0000000040000000 - 0000000040400000 (reserved) (XEN) 0000000040400000 - 000000007bcbd000 (usable) (XEN) 000000007bcbd000 - 000000007bcbe000 (ACPI NVS) (XEN) 000000007bcbe000 - 000000007bcbf000 (reserved) (XEN) 000000007bcbf000 - 000000007bd8e000 (usable) (XEN) 000000007bd8e000 - 000000007bd8f000 (reserved) (XEN) 000000007bd8f000 - 0000000083947000 (usable) (XEN) 0000000083947000 - 0000000084717000 (reserved) (XEN) 0000000084717000 - 0000000084794000 (ACPI data) (XEN) 0000000084794000 - 0000000089834000 (ACPI NVS) (XEN) 0000000089834000 - 0000000089eff000 (reserved) (XEN) 0000000089eff000 - 0000000089f00000 (usable) (XEN) 0000000089f00000 - 000000008f800000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fe000000 - 00000000fe011000 (reserved) (XEN) 00000000fec00000 - 00000000fec01000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000086c800000 (usable) (XEN) ACPI: RSDP 84730000, 0024 (r2 FUJ ) (XEN) ACPI: XSDT 847300A8, 00D4 (r1 FUJ D3644-B1 10600000 AMI 10013) (XEN) ACPI: FACP 84750FE8, 0114 (r6 FUJ D3644-B1 10600000 AMI 10013) (XEN) ACPI: DSDT 84730210, 20DD1 (r2 FUJ D3644-B1 10600000 INTL 20160527) (XEN) ACPI: FACS 89833080, 0040 (XEN) ACPI: APIC 84751100, 0084 (r4 FUJ D3644-B1 10600000 AMI 10013) (XEN) ACPI: FPDT 84751188, 0044 (r1 FUJ D3644-B1 10600000 AMI 10013) (XEN) ACPI: FIDT 847511D0, 009C (r1 FUJ D3644-B1 10600000 AMI 10013) (XEN) ACPI: MCFG 84751270, 003C (r1 FUJ D3644-B1 10600000 MSFT 97) (XEN) ACPI: SSDT 847512B0, 1B1C (r2 CpuRef CpuSsdt 3000 INTL 20160527) (XEN) ACPI: SSDT 84752DD0, 31C6 (r2 SaSsdt SaSsdt 3000 INTL 20160527) (XEN) ACPI: HPET 84755F98, 0038 (r1 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: SSDT 84755FD0, 13FD (r2 INTEL xh_cfsd4 0 INTL 20160527) (XEN) ACPI: UEFI 847573D0, 0042 (r1 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: LPIT 84757418, 0094 (r1 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: SSDT 847574B0, 27DE (r2 FUJ PtidDevc 1000 INTL 20160527) (XEN) ACPI: SSDT 84759C90, 14E2 (r2 FUJ TbtTypeC 0 INTL 20160527) (XEN) ACPI: DBGP 8475B178, 0034 (r1 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: DBG2 8475B1B0, 0054 (r0 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: DMAR 8475B208, 00C8 (r1 INTEL EDK2 2 1000013) (XEN) ACPI: SSDT 8475B2D0, 0144 (r2 Intel ADebTabl 1000 INTL 20160527) (XEN) ACPI: TPM2 8475B418, 0034 (r4 FUJ D3644-B1 1 AMI 0) (XEN) ACPI: ASF! 8475B450, 00A0 (r32 FUJ D3644-B1 10600000 AMI 1000013) (XEN) ACPI: SSDT 8475B4F0, 01A4 (r2 FUJ Gabi0002 2 INTL 20160527) (XEN) ACPI: SSDT 8475B698, 00BB (r2 FUJ Gabi0001 2 INTL 20160527) (XEN) ACPI: WSMT 8475B758, 0028 (r1 FUJ D3644-B1 10600000 AMI 10013) (XEN) System RAM: 32508MB (33289104kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-000000086c800000 (XEN) Domain heap initialised (XEN) Xen WARN at mm.c:5627 (XEN) ----[ Xen-4.11.2-pre x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82d08028e3d0>] ioremap+0xc0/0xd0 (XEN) RFLAGS: 0000000000010002 CONTEXT: hypervisor (XEN) rax: 0000000000000001 rbx: 0000000000000000 rcx: ffff82d08056bc3c (XEN) rdx: ffff82d08056ba84 rsi: 0000000000000000 rdi: 0000000000000000 (XEN) rbp: 0000000000400000 rsp: ffff82d08044fd38 r8: 0000000000001000 (XEN) r9: 0000000000000001 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: ffff82d0803b8000 r13: 0000000100000000 r14: 0000000100000000 (XEN) r15: ffff82d080423db8 cr0: 0000000080050033 cr4: 00000000000000a0 (XEN) cr3: 000000007a244000 cr2: 0000000000000000 (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen code around <ffff82d08028e3d0> (ioremap+0xc0/0xd0): (XEN) 0f 1f 84 00 00 00 00 00 <0f> 0b e9 60 ff ff ff 66 0f 1f 84 00 00 00 00 00 (XEN) Xen stack trace from rsp=ffff82d08044fd38: (XEN) 0000000000000000 0000000000000000 00007d2000000000 00000000007efce4 (XEN) 000000004fffffff ffff82d0803d9682 ffff82d0803b4da0 00000000007efce4 (XEN) 030005504fffffff ffff82d000201540 ffff82d08026b3a0 00000036000000aa (XEN) 00000000007efce4 ffff82d0803e5508 ffff83000009dfb0 ffff83000009df80 (XEN) fffffffffffff001 ffff83000009df00 0000000000000019 000000007a1b9601 (XEN) 0000000000000000 0000000001f44000 ffffffff00000000 000000000086c800 (XEN) ffff83000009df80 ffff82d080423bb0 0000000000000001 0000000000000001 (XEN) 0000000000000001 0000000000000001 0000000000000002 0000000000000002 (XEN) 0000000000000002 000000000009df80 0000000000589000 0000000000588180 (XEN) 00000000000001ff 00000000000001ff 0000000000000000 ffffffd080448000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000004 (XEN) 0000000800000000 000000010000006e 0000000000000003 00000000000002f8 (XEN) 0000000000000000 0000000000000000 000000003fbcebe0 000000003ff25577 (XEN) 0000000000000000 000000007a3bbe04 000000007a1b822e ffff82d0802000f3 (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 0000000000000000 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff82d08028e3d0>] ioremap+0xc0/0xd0 (XEN) [<ffff82d0803d9682>] vesa_init+0x62/0x200 (XEN) [<ffff82d08026b3a0>] vesa.c#lfb_flush+0/0x20 (XEN) [<ffff82d0803e5508>] __start_xen+0x2408/0x2f80 (XEN) [<ffff82d0802000f3>] __high_start+0x53/0x60I'm pretty sure this one is taken care of in 4.11.3; it looks like your gfx card has its frame buffer at an address which is a multiple pf 4Gb. The later crash may then be a result of the earlier issue here. Please retry with 4.11.3, and in case this still fails please also try with 4.13.0-rc5, if at all possible. Jan Attachment:
smime.p7s _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |