[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?
lists@xxxxxxxxxxxx writes: > On Wed, Jul 27, 2016, at 11:36 AM, lists@xxxxxxxxxxxx wrote: >> On Wed, Jul 27, 2016, at 11:28 AM, Andrew Cooper wrote: >> > > I'm not sure if that's good enough. >> > >> > Sadly not. The debug symbols need to be specific to the exact binary >> > you booted. >> > >> > Any change in the compilation will result in the translation being >> > useless. What addr2line is doing is saying "which specific bit of >> > source code did the compiler/linker end up putting at $X". >> >> Got it. Weird that they don't put the .debuginfo rpms in there. >> While I was searching around kernel bug reports over at the distro >> there's lots of posts telling people to debug. Not sure then how >> you do it without the debug symbols. >> >> Guess you have to build your own kernel. > > I got my hands on a 'matched set' > > rpm -qa kernel-default\* > kernel-default-4.7.0-5.1.x86_64 > kernel-default-devel-4.7.0-5.1.x86_64 > kernel-default-debuginfo-4.7.0-5.1.x86_64 > > reboot to Xen, still crashes > > (XEN) [2016-07-28 00:13:18] ----[ Xen-4.7.0_08-452 x86_64 > debug=n Tainted: C ]---- > (XEN) [2016-07-28 00:13:18] CPU: 0 >>>> (XEN) [2016-07-28 00:13:18] RIP: e033:[<ffffffff81f63eb0>] > (XEN) [2016-07-28 00:13:18] RFLAGS: 0000000000000246 EM: 1 > CONTEXT: pv guest (d0v0) > (XEN) [2016-07-28 00:13:18] rax: 0000000000000000 rbx: > 0000000000000000 rcx: 000000016f144000 > (XEN) [2016-07-28 00:13:18] rdx: 0000000100000000 rsi: > 000000016f144000 rdi: fffffffffffff000 > (XEN) [2016-07-28 00:13:18] rbp: 0000000001000000 rsp: > ffffffff81e03e50 r8: ffffffff81efb0c0 > (XEN) [2016-07-28 00:13:18] r9: 0000000000000000 r10: > 0000000000000000 r11: 0000000100000000 > (XEN) [2016-07-28 00:13:18] r12: 0000000000000000 r13: > 0000000000000000 r14: ffffffff81e03f28 > (XEN) [2016-07-28 00:13:18] r15: 0000000000000000 cr0: > 0000000080050033 cr4: 00000000001526e0 > (XEN) [2016-07-28 00:13:18] cr3: 0000000841e06000 cr2: > 0000000000000018 > (XEN) [2016-07-28 00:13:18] ds: 0000 es: 0000 fs: 0000 > gs: 0000 ss: e02b cs: e033 > (XEN) [2016-07-28 00:13:18] Guest stack trace from > rsp=ffffffff81e03e50: > > check ar the RIP addr > > addr2line -e /usr/lib/debug/boot/vmlinux-4.7.0-5-default.debug > ffffffff81f63eb0 > > /usr/src/debug/kernel-default-4.7.0/linux-4.7/linux-obj/../arch/x86/platform/efi/efi.c:123 > > in source > > @ > https://github.com/torvalds/linux/blob/v4.7/arch/x86/platform/efi/efi.c > > ... > void __init efi_find_mirror(void) > { > efi_memory_desc_t *md; > u64 mirror_size = 0, total_size = 0; > > for_each_efi_memory_desc(md) { > unsigned long long start = md->phys_addr; > 123 unsigned long long size = md->num_pages << > EFI_PAGE_SHIFT; > While I see that you're running linux-4.7 could you please double-check that it has the following: commit 55f1ea15216a5a14c96738bd5284100a00ffa9dc Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> Date: Tue May 31 11:23:43 2016 +0100 efi: Fix for_each_efi_memory_desc_in_map() for empty memmaps ? -- Vitaly _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |