From: lists@ssl-mail.com
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Juergen Gross <JGross@suse.com>
Subject: Re: Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?
Date: Wed, 27 Jul 2016 17:28:42 -0700 [thread overview]
Message-ID: <1469665722.1034891.678842041.1A22176B@webmail.messagingengine.com> (raw)
In-Reply-To: <1469644606.3711877.678558833.59B29756@webmail.messagingengine.com>
On Wed, Jul 27, 2016, at 11:36 AM, lists@ssl-mail.com 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;
total_size += size;
if (md->attribute & EFI_MEMORY_MORE_RELIABLE) {
memblock_mark_mirror(start, size);
mirror_size += size;
}
}
if (mirror_size)
pr_info("Memory: %lldM/%lldM mirrored memory\n",
mirror_size>>20, total_size>>20);
}
...
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-28 0:28 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 23:32 Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ? lists
2016-07-27 1:43 ` lists
2016-07-27 15:50 ` Andrew Cooper
2016-07-27 16:21 ` lists
2016-07-27 16:34 ` Andrew Cooper
2016-07-27 16:54 ` lists
2016-07-27 16:56 ` Andrew Cooper
2016-07-27 18:22 ` lists
2016-07-27 18:28 ` Andrew Cooper
2016-07-27 18:36 ` lists
2016-07-28 0:28 ` lists [this message]
2016-07-28 0:53 ` lists
2016-07-28 1:09 ` Konrad Rzeszutek Wilk
2016-07-28 17:20 ` lists
2016-07-28 18:21 ` Daniel Kiper
2016-07-28 18:25 ` lists
2016-07-28 19:05 ` Daniel Kiper
2016-07-28 19:06 ` lists
2016-07-29 14:36 ` lists
2016-07-29 15:42 ` Konrad Rzeszutek Wilk
2016-07-29 15:57 ` lists
2016-07-29 16:03 ` Konrad Rzeszutek Wilk
2016-07-29 16:12 ` lists
2016-08-01 20:11 ` lists
2016-08-01 22:27 ` [BUG] " lists
2016-08-02 6:57 ` Jan Beulich
2016-08-02 13:16 ` lists
2016-08-02 19:02 ` lists
2016-08-03 9:01 ` Jan Beulich
2016-08-03 13:33 ` lists
2016-08-03 13:57 ` Jan Beulich
2016-08-03 14:03 ` Andrew Cooper
2016-08-03 14:50 ` lists
2016-08-03 15:41 ` lists
2016-08-04 15:21 ` lists
2016-07-28 14:09 ` Vitaly Kuznetsov
2016-07-28 14:18 ` lists
2016-07-27 18:33 ` Juergen Gross
2016-08-02 6:36 ` Jan Beulich
2016-08-02 13:13 ` lists
2016-08-02 13:38 ` Jan Beulich
2016-08-02 13:54 ` lists
2016-08-02 14:13 ` Jan Beulich
2016-08-02 14:25 ` lists
2016-08-02 14:50 ` Jan Beulich
2016-08-02 15:04 ` lists
2016-08-02 15:55 ` Jan Beulich
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=1469665722.1034891.678842041.1A22176B@webmail.messagingengine.com \
--to=lists@ssl-mail.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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.